all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <tcross@nospam.une.edu.au>
Subject: Re: face at point
Date: 20 Nov 2002 09:16:51 +1100	[thread overview]
Message-ID: <87ptt12oj0.fsf@blind-bat.une.edu.au> (raw)
In-Reply-To: mailman.1037687132.614.help-gnu-emacs@gnu.org

Eli Zaretskii <eliz@is.elta.co.il> writes:

 
> > From my apropos searches, it seems there is quite
> > a few to choose from and can already see how to make a number of
> > alternatives work
> 
> If the ELisp manual in its node that describes display capabilities 
> doesn't explain how to do what you want, please submit a docs bug 
> report.  Thanks.
> 
Wow, this simple question I asked seems to have really gone off into
intersting tangents. Just to clarify a few things....

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 elisp manual is fine - I can certainly work out how to do this. In
fact, I can work out a number of ways of doing this and this is what
prompted my original question - I was wondering how others do it and
which is better. I've been using emacs for a few years, but am only
now getting into more "power usage" mode and teaching myself elisp
etc. I remembered seeing a thread some time ago here where a debate
broke out regarding why you should not use the window-system variable
to identify the type of system you are on and I was just after some
opinions on this.

With respect to the debate about choices of default colours - I'm
sorry, but I don't think there will ever be a resolution to this sort
of debate - there are too many variables involved, including
individual user taste, hardware, the workstation environment etc. I
think the best the maintainers can do is provide reasonable default
settings and clear documentation and ways of changing these defaults
(which has already been done). The great wonder of emacs is that the
user can customize all of this very easily, so long debates about the
default colours don't seem very productive (except in the academic
sense - always like a good debate). 

The one thing I'm very happy about and what I've always loved about X
and unix is that at least in most cases you can change default colour
settings and the changes are consistent. I am continually frustrated
in the Windows world where I define a colour scheme which I find
comfortable to work with only to find some applications only obey the
background settings for my scheme and ignore the foreground settings,
resulting in white on white or black on black or some other unreadable
combination!

Tim

       reply	other threads:[~2002-11-19 22:16 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 ` Tim Cross [this message]
2002-11-20  5:47   ` face at point Eli Zaretskii
2002-11-20 11:06   ` Oliver Scholz
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

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

  git send-email \
    --in-reply-to=87ptt12oj0.fsf@blind-bat.une.edu.au \
    --to=tcross@nospam.une.edu.au \
    /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.