From: Eli Zaretskii <eliz@gnu.org>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: jporterbugs@gmail.com, gregory@heytings.org, 62370@debbugs.gnu.org
Subject: bug#62370: 28.1; sieve-mode: faces should inherit from font-lock-X-face faces
Date: Thu, 23 Mar 2023 08:58:09 +0200 [thread overview]
Message-ID: <83jzz854zi.fsf@gnu.org> (raw)
In-Reply-To: <ZBul1PojSCiyyZ2B@hera.lan> (trentbuck@gmail.com)
> Date: Thu, 23 Mar 2023 12:05:24 +1100
> From: "Trent W. Buck" <trentbuck@gmail.com>
> Cc: Gregory Heytings <gregory@heytings.org>, Eli Zaretskii <eliz@gnu.org>,
> 62370@debbugs.gnu.org
>
> I don't think "I opened foo.sieve in Emacs 20 twenty years ago, and
> now I opened foo.sieve in Emacs 30 today, and the colors aren't identical, and now I'm mad"
> is a good argument for never changing the defaults.
From my POV, it _is_ a good argument. Especially when the defaults
change in a feature that is easily customizable, and so basically you
are asking to impose your preferences, which are easily catered to by
your local customizations, on everyone else.
> Emacs changes the defaults like that ALL THE TIME.
That's not true. We do that rarely and sparingly, precisely for the
reasons you consider unimportant.
> If they piss me off, I just patch back in the old behaviour and forget about it.
You can do the same with the current defaults, so why are you asking
us to change them?
next prev parent reply other threads:[~2023-03-23 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 5:41 bug#62370: 28.1; sieve-mode: faces should inherit from font-lock-X-face faces Trent W. Buck
2023-03-22 14:49 ` Eli Zaretskii
2023-03-22 20:10 ` Gregory Heytings
2023-03-22 21:22 ` Jim Porter
2023-03-23 1:05 ` Trent W. Buck
2023-03-23 6:58 ` Eli Zaretskii [this message]
2023-03-23 7:03 ` Trent W. Buck
2023-03-23 7:25 ` Eli Zaretskii
2023-03-23 16:11 ` Jim Porter
2023-09-03 10:30 ` Stefan Kangas
2023-09-03 11:04 ` Philip Kaludercic
2023-09-05 4:43 ` Jim Porter
2023-09-05 12:01 ` Eli Zaretskii
2023-09-05 15:52 ` Jim Porter
2023-09-05 16:17 ` 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=83jzz854zi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62370@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=jporterbugs@gmail.com \
--cc=trentbuck@gmail.com \
/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).