The last two years have seen @clean and the clone-find commands.  Both are 
game changers. My *goal *for the new year is create something similar.

The *strategy *will be to focus on problems that we have learning or using 
Leo.  Some possibilities:



*Learning about Leo*The Programming with Leo 
<http://leoeditor.com/tutorial-programming.html> tutorial must be 
rewritten, following the "less said the better" principle. I'll start with 
motivating @file and @others.  Everything else is details.

I am considering a series of "Looking over Edward's shoulder" tutorials.  
Instead of slideshows or videos, it may be more effective to throw out a 
few haiku-like invitations for discovery, following the how to learn Leo 
post <https://groups.google.com/forum/#!topic/leo-editor/aafVEBcF9q4>. Yes, 
Leo has a gazillion features, but the basics of Leo are simple, and there 
aren't many of them.

*Editing*

Leo might benefit from a temporary vim mode.  This should be easy to do, 
and it might be useful in some situations.  Leo might also benefit from a 
vim-like "dot" command.

I am having my doubts that a super-duper outline-based diff 
<https://groups.google.com/forum/#!topic/leo-editor/ZKP-X2kCc9s> is going 
to be useful. The only time I ever use git diff is when creating a checkin 
log. Still, I'll investigate a bit further.

As always, I'll be looking for ways to better integrate Leo with vim, 
emacs, jupyter, etc.

*Testing*

The TDD advances 
<https://groups.google.com/forum/#!topic/leo-editor/UCcBz-BdHII>, have 
stimulated further thoughts. More improvements may follow.

Leo is a uniquely friendly environment for unit testing.  For example, one 
could imagine a short script that would generate unit tests for all 
commands, or all methods in a file or class.

*Design and checking*

After spending considerable time writing the make-stub-files 
<https://github.com/edreamleo/make-stub-files> script, I have never used 
mypy <http://mypy-lang.org/>. I'll probably play around with checking next 
year.  Programmers have not begun to use big data to validate/improve their 
programs...

*Understanding*

The biggest payoff may come from enhancing Leo's unique strength, namely 
understanding computer programs, or other complex data.  Advances in this 
arena will be difficult (impossible) to duplicate in other programs.

That's all for now.  All comments welcome.

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.

Reply via email to