On Sun, Mar 6, 2016 at 7:06 PM, SegundoBob <[email protected]> wrote:
>
For almost all commands, print-commands tells you something about the
command because the commands contain at least some full works. For
example, search-forward and search-backward. These new cf* commands are
inconsistent with this pattern.
Thanks for this.
In the code, it arises because, for example, cff is defined as follows:
@cmd('clone-find-all-flattened')
@cmd('find-clone-all-flattened')
@cmd('cff')
def minibufferCloneFindAllFlattened...
...no docstring!
So there is no help for *any* of these commands. I'll fix this today.
>
Finally, I tried Alt-H, D (open LeoDocs.leo) and I found good documentation
for the cf* commands.
Oh good. That will be the basis for the the docstrings.
> I think it is annoying that F11 (Help for command) has no help for some
commands.
There is a script somewhere that warns about missing docstrings. Oh, I
remember, it's a pylint warning. I could enable that, but it would be more
useful to write a leo script that warns when a decorated function/method
has no docstring. This is one of those things that should be done for
5.2b1.
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
