From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: emacs -q -nw --color=never
Date: Sat, 27 Sep 2003 14:18:05 +0200 [thread overview]
Message-ID: <7494-Sat27Sep2003141804+0300-eliz@elta.co.il> (raw)
In-Reply-To: <E1A2fPA-0000Kq-HO@fencepost.gnu.org> (message from Richard Stallman on Thu, 25 Sep 2003 19:20:12 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Thu, 25 Sep 2003 19:20:12 -0400
> X-PRIVAWALL-ID: 0002556710ac
> X-OriginalArrivalTime: 26 Sep 2003 00:23:17.0468 (UTC) FILETIME=[61D4F1C0:01C383C4]
>
> > /* Canonicalize negative numbers to -1. */
> > if (mode < 0)
> > mode = -1;
>
> I don't really object, but what problem would that solve? The value
> of `mode' is not supposed to be negative unless it's -1.
>
> That's the point--a user could specify -2 or -1000.
> It may as well do something predictable.
The current code does something predictable as well: any number that
is not a positive number of colors and not -1 means the same as zero,
i.e. switch to the default number of colors, the one specified by the
terminal's termcap/terminfo entry. (The code that does that is in
tty_setup_colors.)
Thus,
emacs -nw --color=2000
and
emacs -nw --color=-2000
produce the same result. What you suggest will change that.
Do you think that negative arguments are ``special'' in the sense that
they imply that the feature is to be turned off?
(I should also add that the user is not supposed to use numbers as
arguments to the --color option, except if she specifies the number of
supported colors, like --colors=8 or --colors=256. That is, I never
meant for them to say --colors=-1 or --colors=0, since the expected
effect of --colors=0 might be to turn off the colors, which is not
what happens. Similarly, --colors=-2000 was not something I expected
users to say.)
next prev parent reply other threads:[~2003-09-27 12:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 18:48 emacs -q -nw --color=never Luc Teirlinck
2003-09-21 19:31 ` emacs and libxml2 (for emacs w3) Nic Ferrier
2003-09-22 9:05 ` Richard Stallman
2003-09-23 11:05 ` Nic Ferrier
2003-09-24 8:41 ` Richard Stallman
2003-09-24 11:14 ` James Clark
2003-09-24 12:42 ` Stefan Monnier
2003-09-24 19:35 ` Nic Ferrier
2003-09-25 5:31 ` James Clark
2003-09-25 23:45 ` Alex Schroeder
2003-09-21 23:02 ` emacs -q -nw --color=never Robert J. Chassell
2003-09-22 9:05 ` Richard Stallman
2003-09-22 16:48 ` Eli Zaretskii
2003-09-22 17:04 ` Eli Zaretskii
2003-09-22 16:47 ` Luc Teirlinck
2003-09-24 12:47 ` Richard Stallman
2003-09-24 18:35 ` Eli Zaretskii
2003-09-25 23:20 ` Richard Stallman
2003-09-27 12:18 ` Eli Zaretskii [this message]
2003-09-28 15:34 ` Richard Stallman
2003-09-28 21:50 ` Eli Zaretskii
2003-09-29 19:31 ` Richard Stallman
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=7494-Sat27Sep2003141804+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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).