On Nov 15, 9:11 am, "Edward K. Ream" <[email protected]> wrote: > For the last few days Leo's add-comment command has put comment > delimiters at the left edge. This was a side effect of fixing the > command for languages like html do not have single-line comment > delimiters. I did not like this new way of working at all. > > Today I restored Leo's legacy operation (minus the bug) by adding the > @bool indent_added_comments setting, with default True.
A few weeks ago I took a look at Fernando Perez's docstrings for IPython. Impressive. Docstrings, and F1 (help-for-command), may be the middle ground that resolves the tension between Kent's desire for documentation and my belief that nobody reads them. As a minimal standard, the docstring for a command should mention all settings that pertain to that command. We would like people to get in the habit of doing F1 if a command doesn't work as expected, or just to explore what Leo can do. As an improved standard, we would like the docstring to contain all info contained in Leo's docs, and vice versa. I'll start this never-ending project by upgrading the docstrings for add-comments and delete-comments. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
