I'd find a console interface really useful as well. I know about sshfs and that
can help in some cases, but there are cases where Shell-in-a-box (web based
shell client) is about a much access as you can usefully get, and then console
Leo would be great (console apps. like nano and mc work, so it has good console
support).
Leo has an interface abstraction layer like you refer to John, but I think
you're right that you don't really test something like that without the
existence of multiple active interfaces. Then of course there are plugins, a
lot of them go straight to native Qt, inevitably. But even console leo with no
plugins would be pretty cool.
Some of Leo's strengths make things more challenging, key handling that works
not just in the body text but in some widgets (esp. headlines) too, that kind
of thing.
Where's the sweet spot between a de novo interface that just uses leoserver to
push things into and out of Leo, or Leo's internal abstraction so that there's
at least the potential for something to work across interfaces.
Cheers -Terry
From: john lunzer <[email protected]>
To: leo-editor <[email protected]>
Sent: Friday, November 18, 2016 11:13 AM
Subject: Why I don't use Leo more often
I use Leo as my primary editor when I can.
When I can't is when I'm SSHing into machines remotely where it is often not
practical (or desirable) to run GUI applications. I believe there was some work
done on a curses front-end plugin in the past but I'm not sure how far that got.
I would eventually like to see a full fledged console front-end for Leo. I have
no illusions about it popping up by magic.
I would only say, if, by chance, work begins on a new web-based front-end, that
might be an opportunity to rework/simplify the back-end interface/API which
would work towards the "leo as a plug-in" long term goal. This might make it
easier to implement a console front-end with something like urwid.
Emacs can be run in a daemon mode where multiple front-end clients can connect
to a single instance of an emacs "server". I envision a future Leo with a
similar capability, where a back-end/front-end protocol is devised and you
could connect any number and type of front-end clients to the back end.--
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.
--
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.
