all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Ag Ibragimov <agzam.ibragimov@gmail.com>, emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Regarding on-key-up event
Date: Sat, 4 Feb 2023 10:47:56 -0500	[thread overview]
Message-ID: <CAO2hHWYJY7NApV6Rn-d+Z2gVAXGd+LEhMVJKCYMbr0V6ZeMcJw@mail.gmail.com> (raw)
In-Reply-To: <834js1vrdw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

In general, emacs is not interacting with the hardware at the level you're
talking about -- if it were, then emacs would have to (re-)implement things
like compose-keys that definitely belong at the system level. For emacs, as
I understand it, each window system or terminal maps the
specific interface to emacs' typical interface. By way of example, look at
pgtk_gtk_to_emacs_modifiers in pgtkterm.c, which is pretty simple because
the GTK interface is built on the GDK interface which grew more or less
directly out of the X11 interface, which also birthed emacs' internal
interface _for gui code_, but is not the same thing that emacs gets from
terminal interfaces. This last bit is why, for example, Control-I,
Control-[, and Control-Shift-Z are "tricky" for console emacs.

Another way to put it: despite the rumors/memes/stories, emacs isn't
actually an operating system (although it's not impossible to think of it
as a restricted virtual OS layered above the actual OS). It's probably
possible to change emacs to make it closer to the low-level interface for a
specific combination of UI and OS, and it would almost certainly break some
abstractions for other combinations.

I hope this helps,
~Chad

[-- Attachment #2: Type: text/html, Size: 1326 bytes --]

      reply	other threads:[~2023-02-04 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 17:31 Regarding on-key-up event Ag Ibragimov
2023-02-03 18:18 ` Eli Zaretskii
2023-02-03 19:25   ` Ag Ibragimov
2023-02-03 19:39     ` Eli Zaretskii
2023-02-03 21:47       ` Konstantin Kharlamov
2023-02-03 22:05         ` Konstantin Kharlamov
2023-02-04  0:18         ` Po Lu
2023-02-04  0:48           ` Ag Ibragimov
2023-02-04  1:26             ` Po Lu
2023-02-04  7:07         ` Eli Zaretskii
2023-02-03 23:45       ` Ag Ibragimov
2023-02-04  0:34         ` Po Lu
2023-02-04  7:09         ` Eli Zaretskii
2023-02-04 15:47           ` chad [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO2hHWYJY7NApV6Rn-d+Z2gVAXGd+LEhMVJKCYMbr0V6ZeMcJw@mail.gmail.com \
    --to=yandros@gmail.com \
    --cc=agzam.ibragimov@gmail.com \
    --cc=eliz@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.