[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why bring new features to Emacs and not Emacs to new applications?
From: |
Pascal J. Bourguignon |
Subject: |
Re: Why bring new features to Emacs and not Emacs to new applications? |
Date: |
Mon, 25 Nov 2013 21:12:12 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Lennart Borgman <address@hidden> writes:
> On Mon, Nov 25, 2013 at 12:37 AM, Pascal J. Bourguignon
> <address@hidden> 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/