Re: Why bring new features to Emacs and not Emacs to new applications?

[Lennart Borgman <lennart.borgman@gmail.com>]

On Mon, Nov 25, 2013 at 9:12 PM, Pascal J. Bourguignon
<pjb@informatimago.com> wrote:
> 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.

I meant on a lower level in the C code, but I do not remember the
details any more.