On Sat, Dec 11, 2021 at 10:31 AM vitalije <[email protected]> wrote:
I was absent for the last few days. Regarding async def problem, I believe > that would be an easy fix/addition. I know that at-others some times can be > at the zero indentation and most of the children have extra indentation. > This is supposed to happen only if indenting at-others would lead to the > indentation of under-indented comments and therefore would cause the > difference between the source code and the code outline would produce. This > was intentional. > I see. My preference is to base the indentation of @others on the first *significant *line that follows the "class" line. In that case, the python importer may be forced to insert the underindented escape sequence. > I will check to see why those files have this problem, and if it is caused > by under indented comments I would rather let user manually fix this > indentation problem. The next time the file is imported it would have usual > form (indented at-others and not indented children). However, this might > also be a matter of setting/preference too. > I am happy to "promote" underindented comments as required. In my importer, this is (would be?) done by not adding the underindented escape sequence before comment lines. I'll investigate further and will report my findings later. > Thanks. I am enjoying this conversation. The python importer presents subtle problems, and it's good to see alternative solutions. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS1R%3D%3DRJcs4S%2BbRsav7k7FquiSn%2B3pSgQM-Dracnd71MRA%40mail.gmail.com.
