From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: how to use graphic-display-p and window-system
Date: Fri, 17 Apr 2009 17:19:51 -0700 [thread overview]
Message-ID: <001201c9bfbb$65707c30$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <jwvy6tyluf0.fsf-monnier+emacs@gnu.org>
> The general solution is to not try to answer the question:
> instead, make
> sure you provide a "guaranteed" binding (i.e. a binding that only uses
> keys that are known to work pretty much everywhere),
And those are? And that is described where?
> and once that's done you may also provide another binding
> using a less standard key.
That's exactly what I'm doing. But I want to make that basic binding the
default, when the context is unlikely to not support the fancier keys.
That's why I'm looking for a general, heuristic test - likeliness, not
certainty. I'm not looking for something that is always "correct", but for a
test that lets me choose a reasonable default. Users can of course use whatever
keys they want, but a default binding that is reasonable most of the time can be
helpful.
> > 1. General colors vs no colors or limited set of colors (e.g. 256).
>
> `display-color-cells'.
>
> > 2. General keys vs no modifiers for keys such as TAB, insert, and
> > prior. This means also distinguishing between, say, C-l
> > and C-S-l.
>
> Fundamentally impossible.
Are you talking about the first sentence, the second, or both?
For the first, as far as I can see, Emacs source code does this in various
places, and it seems to use `window-system' to do it. No doubt that is not 100%
accurate, but I don't need such accuracy either.
For the second, it's certainly not impossible to bind different commands to C-l
and C-S-l, if that's what you meant.
next prev parent reply other threads:[~2009-04-18 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m28wm31ock.fsf@nschum.de>
[not found] ` <834owro4ha.fsf@gnu.org>
2009-04-17 17:37 ` how to use graphic-display-p and window-system Drew Adams
2009-04-17 18:15 ` Eli Zaretskii
2009-04-17 20:15 ` Drew Adams
2009-04-17 23:54 ` Stefan Monnier
2009-04-18 0:19 ` Drew Adams [this message]
2009-04-18 3:41 ` Stefan Monnier
2009-04-18 4:25 ` Drew Adams
2009-04-18 0:21 ` Miles Bader
2009-04-18 3:43 ` Stefan Monnier
2009-04-18 4:24 ` Drew Adams
2009-04-18 5:11 ` Miles Bader
2009-04-18 6:34 ` Eli Zaretskii
2009-04-18 7:01 ` Eli Zaretskii
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='001201c9bfbb$65707c30$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).