From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: face at point
Date: Wed, 20 Nov 2002 12:06:04 +0100 [thread overview]
Message-ID: <u1y5go603.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: 87ptt12oj0.fsf@blind-bat.une.edu.au
Tim Cross <tcross@nospam.une.edu.au> writes:
[...]
> All I really wanted to know was "Which is the best/most
> appropriate/accepted way of distinguishing between emacs running on a
> tty, in its own X frame and within an X term so that I can set my
> colours accordingly.
[...]
The reason to use a check for specific display capabilities with the
`display-.*-p' functions is, that Emacs' capabilities on different
displays/operating systems may change in the future as well as the
operating systems/displays themselves. Even the distinction between a
tty and a graphical display may become more and more blurred. An xterm
may already display 256 colours, why not a future Linux console, too?
Why not real face attributes like bold and italic on a future console?
Emacs 20 did not display colours on a Linux console, for example, but
Emacs 21 does. Or the other way around: Emacs 21.2 does not display
images on MS Windows, although this is a graphical display. But Emacs
21.4 will do.
When you check for display capabilities as needed, you play safe. You
don't have to change your package or your .emacs according to the
display capabilities du jour. Therefore it is depreciated to check for
a specific display or operating system via `window-system' or some
such. In other words: there is no "appropriate/accepted way" to do
this.
Oliver
--
30 Brumaire an 211 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2002-11-20 11:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1037687132.614.help-gnu-emacs@gnu.org>
2002-11-19 22:16 ` face at point Tim Cross
2002-11-20 5:47 ` Eli Zaretskii
2002-11-20 11:06 ` Oliver Scholz [this message]
2002-11-20 14:01 ` Stefan Monnier <foo@acm.com>
2002-11-20 16:00 ` Michael Slass
[not found] <mailman.1037771296.12946.help-gnu-emacs@gnu.org>
2002-11-20 7:34 ` Miles Bader
2002-11-20 7:39 ` Kai Großjohann
[not found] ` <mailman.1037777785.20916.help-gnu-emacs@gnu.org>
2002-11-20 11:10 ` Oliver Scholz
[not found] <mailman.1037688495.14173.help-gnu-emacs@gnu.org>
2002-11-19 8:54 ` Fredrik Staxeng
2002-11-19 18:14 ` Eli Zaretskii
[not found] ` <mailman.1037733383.18353.help-gnu-emacs@gnu.org>
2002-11-20 13:37 ` Fredrik Staxeng
2002-11-20 16:13 ` Eli Zaretskii
[not found] ` <mailman.1037812462.4160.help-gnu-emacs@gnu.org>
2002-11-20 17:56 ` Fredrik Staxeng
2002-11-15 2:13 John Hunter
2002-11-15 2:50 ` Jesper Harder
2002-11-15 3:30 ` John Hunter
2002-11-15 3:40 ` Jesper Harder
2002-11-15 10:24 ` Oliver Scholz
2002-11-15 13:37 ` Jesper Harder
2002-11-15 14:51 ` Jesper Harder
2002-11-15 16:58 ` Oliver Scholz
2002-11-16 18:49 ` Kai Großjohann
2002-11-15 4:24 ` Miles Bader
[not found] ` <mailman.1037335988.3983.help-gnu-emacs@gnu.org>
2002-11-15 14:21 ` Michael J Downes
2002-11-15 14:31 ` John Hunter
2002-11-17 22:40 ` Tim Cross
2002-11-17 23:00 ` Miles Bader
2002-11-18 5:54 ` Tim Cross
2002-11-18 8:52 ` Miles Bader
[not found] ` <mailman.1037610573.27378.help-gnu-emacs@gnu.org>
2002-11-18 13:48 ` Fredrik Staxeng
2002-11-18 17:23 ` Oliver Scholz
2002-11-18 18:16 ` Fredrik Staxeng
2002-11-18 17:56 ` Eli Zaretskii
[not found] ` <mailman.1037646827.31512.help-gnu-emacs@gnu.org>
2002-11-19 6:02 ` Fredrik Staxeng
2002-11-19 6:47 ` Eli Zaretskii
2002-11-19 9:20 ` Miles Bader
2002-11-19 20:24 ` Kai Großjohann
2002-11-18 22:06 ` Tim Cross
2002-11-18 22:36 ` Jesper Harder
2002-11-19 2:00 ` Miles Bader
2002-11-19 1:55 ` Miles Bader
2002-11-19 5:31 ` Eli Zaretskii
[not found] ` <mailman.1037671096.385.help-gnu-emacs@gnu.org>
2002-11-19 5:58 ` Tim Cross
2002-11-19 6:24 ` Eli Zaretskii
2002-11-19 6:24 ` Fredrik Staxeng
2002-11-19 6:56 ` Eli Zaretskii
2002-11-19 8:56 ` Miles Bader
[not found] ` <mailman.1037696237.22239.help-gnu-emacs@gnu.org>
2002-11-19 9:46 ` Fredrik Staxeng
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=u1y5go603.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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.
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).