On 3/15/2015 7:57 PM, Ross Burnett wrote:
I'm an old dog trying to learn new tricks. I have been learning
Python and using PyCharm IDE when I discovered Leo. I use Win 7 on a
fast PC I assembled myself. I have been a Cobol developer since the
early 70's but now more of a systems consultant for a huge
state-funded system written in Cobol. I have never used Linux or
Emacs or Vim - just MS stuff mostly, plus IBM mainframe editors, and
EditPlus, a very nifty programming editor.
Welcome!
I was excited to find Leo, but after struggling with Leo for 2 days,
here are some questions/comments/complaints:
When is the Leo Editor for Dummies book coming out?
Probably fifth of never... but the tutorials are fairly decent at this
point :)
How can I have Leo re-open all the leo files I was last viewing when I
closed Leo? Shouldn't that be the default mode? Why is workbook.leo
the default?
I did find the Leo file directive and changed it in myleosettings to
open my own work file. Is that the only way to have a file
automatically load?
There is the 'session' feature. Why this is not enabled by default, I
do not know. Details here:
http://leoeditor.com/running.html?highlight=session#using-sessions
In Tutorial Basics / Finding & replacing text:
"Ctrl-F and type "def" in the minibuffer."
I was confused because this is not the field named "Minibuffer" in
the Body, but the text entry box next to 'Find:'.
Is this is an Emacs term? Suggestion: define minibuffer at top of
tutorial for the many who have no idea what Emacs is.
When I press ctrl-F in the Body, the find minibuffer does not get
the cursor, so I need to click on that field?
This is probably from the old times, when the search functionality used
the minibuffer rather than the search tab. I'm not sure what's up with
the focus issue -- Edward will have to chime in on that one.
Personal settings in myLeoSettings:
after changing a setting value, do I need to close and reopen Leo
for it to take effect, or is there a shortcut? 'Settings/Reload
settings' seems to have no effect.
In general, yes, you need to restart Leo, or at least load a new .leo
file. I'm not sure what that menu item does -- I've never noticed it
before!
"Creating external files with @file and @all" (
http://leoeditor.com/tutorial-basics.html#id15 )
There is no explanation for where the @all directive should be
placed - where does it go?
It should be in the body of an @file node. Edward -- is this a
documentation miss?
When creating a new leo file, Save brings up the master leo directory?
('Master' meaning the directory where Leo is installed.) How do I
change this default to use My Documents/Leo directory? Shouldn't a
personal directory be the default for new leo files? Same question
for the 'Open'.
Leo's open/save dialogs tend to use whichever directory Leo was launched
from. I'm not sure if there's a way to change this behavior.
Using Leo as a PIM / Clones
(http://leoeditor.com/tutorial-pim.html#id1 ):
Ctrl-` (clone-node) : I couldn't get this to work because I
thought that was a single quote.
It would be _very_ helpful to explain that character is the Grave
Accent, a character I don't remember ever using. Ever.
The docs used to mention that this was the same key as the tilde (~).
Not sure if they do anymore. Sorry for the confusion!
Urls in the Body are not 'active' - I can't double-click and have the
url open in browser - is that normal?
Yes, that's normal. Ctrl+click does the trick, though.
I downloaded Python.leo from Sourceforge. When I open that in Leo, the
log says that the settings were read, but nothing is displayed in
Outline or Body. I was able to view Books and PyDoc from Sourceforge.
Why is Python.leo not displayed?
I'm not sure what Python.leo is... I also don't use sourceforge myself,
so someone else should chime in here.
Finally, there is some mysterious key combination that makes the
outline disappear, and makes Leo unresponsive to any further file
operation. This has happened twice. What is going on with that? I
have to use the Task Manager to force Leo to close, and lose my updates.
Please experiment to figure out what key binding it is and file a bug,
including your environment info (OS, python version, pyqt version, etc.)
: https://github.com/leo-editor/leo-editor/issues
There just seems so much to learn, and it seems like all the
documentation is written with a great deal of assumed prior knowledge.
I despair of ever mastering this, and that makes me sad because Leo
is obviously a fantastic piece of software. Maybe with a Leo for
Dummies book...
It's a large and complex project. There's no doubt that the learning
curve is rough, but we're doing what we can... The docs are much better
than they used to be (Edward's made leaps and bounds over the prior
state), but documentation could always be better. Any specific
suggestions are always welcomed -- action items tend to get worked on
around here :)
Hope this helps!
-->Jake
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
