On 11/22/2013 2:12 PM, Matt Wilkie wrote:
Jake, would you please elaborate on your objection to "command line"?
Conceptually for me that is what it is "Leo's command line". If
anything I would like to see it become even more of a command line
than it is now, with command history etc., like vim. (For what it's
worth vim calls its equivalent a command-line,
http://vimhelp.appspot.com/cmdline.txt.html#Command-line)
Huh, I always thought Vim called it 'command mode' without a name for
where you typed the commands in (since *all* keyboard output is
redirected there while in command mode, there doesn't really need to be
a name, does there?).
Anyways, command line to me indicates the interface one uses within the
OS shell of their choice to manipulate a program's behavior. The place
where one types flags and provides arguments. This doesn't mesh well
with the idea of the minibuffer, unless you're considering Leo a shell
on it's own, and the commands you're firing to be mini programs... which
makes a lot of sense, now that I think about it.
How about 'the Leo Shell'? This encapsulates all the good ideas and
prevents the weirdness of 'minibuffer'...
Also, I agree, it needs history, etc. But more like bash, IMO, than
vim, really.
-->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/groups/opt_out.
