From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: emacs-devel@gnu.org
Subject: Re: Why bring new features to Emacs and not Emacs to new applications?
Date: Mon, 25 Nov 2013 21:12:12 +0100 [thread overview]
Message-ID: <878uwctf4z.fsf@informatimago.com> (raw)
In-Reply-To: CANbX366LWbMrO1ujvpJ6BzRyra_7PVxrduo9ivkqVE45KiXDzA@mail.gmail.com
Lennart Borgman <lennart.borgman@gmail.com> writes:
> On Mon, Nov 25, 2013 at 12:37 AM, Pascal J. Bourguignon
> <pjb@informatimago.com> wrote:
>>
>>>> - incompatible control structure.
>>>>
>>>> While most applications will have like emacs a main event loop, it is
>>>> not designed usually to go thru (dynamically modifiable) keymaps to
>>>> handle in a uniform way the events, but would rather rely on
>>>> frameworks, which may implement their own modal control loops.
>>>
>>> Isn't this an area where Emacs must change?
>>
>> On the contrary, this is the essence of what an emacs is.
>
> I think we are misunderstanding each other. There are all sort of
> events that must be handled. Isn't there loops inside the keyboard
> handling now? (Or, do I misremember?)
Not really. There's function like read-from-minibuffer, but they're
called explicitely by the commands that are called when receiving
commands asking for minibuffer input, like M-x =
execute-extended-command.
Also, there's what's called recursive edit, where one command loop calls
another embedded command loop, but since it's just a recursive call, it
wouldn't really qualify as a modal loop.
--
__Pascal Bourguignon__
http://www.informatimago.com/
next prev parent reply other threads:[~2013-11-25 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 18:38 Why bring new features to Emacs and not Emacs to new applications? (was: Emacs as word processor) Torsten Wagner
2013-11-24 21:00 ` Why bring new features to Emacs and not Emacs to new applications? Pascal J. Bourguignon
2013-11-24 21:20 ` Lennart Borgman
2013-11-24 23:37 ` Pascal J. Bourguignon
2013-11-25 1:20 ` Lennart Borgman
2013-11-25 20:12 ` Pascal J. Bourguignon [this message]
2013-11-25 21:14 ` Lennart Borgman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878uwctf4z.fsf@informatimago.com \
--to=pjb@informatimago.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).