From: David Kastrup <dak@gnu.org>
Cc: Kevin Rodgers <ihs_4664@yahoo.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: re-builder highlighting incorrect for more than 3 groupings
Date: Tue, 02 May 2006 11:38:26 +0200 [thread overview]
Message-ID: <85r73csr59.fsf@lola.goethe.zz> (raw)
In-Reply-To: <f7ccd24b0605020230s5f49a17bjf96b23223b702a07@mail.gmail.com> (Juanma Barranquero's message of "Tue, 2 May 2006 11:30:22 +0200")
"Juanma Barranquero" <lekktu@gmail.com> writes:
> On 5/2/06, David Kastrup <dak@gnu.org> wrote:
>
>> A complete waste of code for no apparent good whatsoever.
>
> Then remove the definitions for faces reb-match-[1-3]. reb-match-0
> should suffice. At the very least, reb-match-[2,3] are unnecessary,
> from a zen-minimalistic POV.
The cycling patch was not reducing the number of distinct colors:
there never was a proposal to add more _distinct_ colors to the
standard scheme.
That's what "no apparent good whatsoever" is about: just defining more
faces in a cyclic fashion does not change the appearance in any way.
> Not to mention that "no apparent good whatsoever" is highly
> subjective, isn't it?
No, it isn't. If the colors are the same anyway, there is no point in
attaining that effect in a more verbose manner.
>> So what? It is not like the cycling code would keep them from doing
>> that if they want to.
>
> No. But I think we could agree that there are at least three criteria
> (perhaps more) to define something as a good default for Emacs:
>
> - Defaulting to that something makes Emacs safer out-of-the-box
> - Defaulting to that something is easier to understand for a newbie
> - If not a default, most people interested in the feature will set
> or define that something in their .emacs
>
> I was hypothesizing about the third condition.
So what? You have not given _any_ kind of rationale where this third
condition would in any way be affected. Users can define more colors
if they really want to.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-05-02 9:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 19:40 re-builder highlighting incorrect for more than 3 groupings Christian Plate
2006-04-26 6:56 ` martin rudalics
2006-04-27 4:36 ` Richard Stallman
2006-04-27 8:55 ` martin rudalics
2006-04-27 9:04 ` Juanma Barranquero
2006-04-28 22:03 ` Adrian Aichner
2006-04-28 23:23 ` Juanma Barranquero
2006-04-29 19:09 ` Richard Stallman
2006-04-29 20:36 ` Adrian Aichner
2006-04-30 1:02 ` Juanma Barranquero
2006-04-29 8:12 ` martin rudalics
2006-04-30 1:07 ` Juanma Barranquero
2006-04-30 3:03 ` Richard Stallman
2006-05-01 15:21 ` Kevin Rodgers
2006-05-02 2:04 ` Richard Stallman
2006-05-02 8:42 ` Juanma Barranquero
2006-05-02 9:06 ` David Kastrup
2006-05-02 9:30 ` Juanma Barranquero
2006-05-02 9:38 ` David Kastrup [this message]
2006-05-02 10:17 ` Juanma Barranquero
2006-05-02 21:37 ` 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=85r73csr59.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ihs_4664@yahoo.com \
--cc=rms@gnu.org \
/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).