From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>, <help-gnu-emacs@gnu.org>
Subject: RE: What is keyboard-local?
Date: Fri, 15 Feb 2013 09:27:03 -0800 [thread overview]
Message-ID: <9F574A0FEC1F4563BFCCA3A065AFC0FC@us.oracle.com> (raw)
In-Reply-To: <jwvd2w13ax5.fsf-monnier+gnu.emacs.help@gnu.org>
> Actually, there are no real "terminal-local" variables, since
> all those are in reality keyboard-local.
>
> Emacs's "terminals" are visible in Elisp (e.g. `frame-terminal'
> returns the "terminal" from where a particular frame comes).
>
> OTOH Emacs's "keyboards" are not directly visible. A "keyboard"
> belongs to a particular terminal, but terminals can have several
> "keyboards", although in practice 99.99% of the terminals have
> only 1 keyboard.
>
> IIRC the only cases where you can have several keyboards for a given
> terminal, is when you have an X11 server (e.g. "foo:0") with various
> "X11 screens" (i.e. you have foo:0.0 and foo:0.1) in which case each
> X11 screen gets a corresponding Emacs "keyboard", whereas they
> all share the same Emacs "terminal".
>
> I'm pretty sure this subtlety is not handled correctly everywhere in
> Emacs (IOW we have bugs in there). We should probably get rid of
> this distinction.
While waiting for such a code fix, at least, please consider updating the doc
with info such as you just provided here, unless you feel it is already there
somewhere.
next prev parent reply other threads:[~2013-02-15 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19491.1360502173.855.help-gnu-emacs@gnu.org>
2013-02-12 13:15 ` What is keyboard-local? Michael Heerdegen
[not found] ` <mailman.19668.1360674873.855.help-gnu-emacs@gnu.org>
2013-02-15 14:41 ` Stefan Monnier
2013-02-15 17:27 ` Drew Adams [this message]
2013-02-10 13:15 Xue Fuqiao
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=9F574A0FEC1F4563BFCCA3A065AFC0FC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.