From: Radon Rosborough <radon.neon@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] Only signal package.el warnings when needed
Date: Mon, 21 Jan 2019 14:45:36 -0800 [thread overview]
Message-ID: <CADB4rJEk+cd-LuB6Lce0W6y2_2vtFtULyw9Xwhy9cVZz-GeudA@mail.gmail.com> (raw)
In-Reply-To: <83tvi9d8o8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
> That there's some fallout cannot be used as an ultimate argument in
> favor or against some change.
In that case, could you explain what /would/ be a good argument in
favor or against the change I am proposing? As far as I can tell, it
saves people time without any known disadvantages (and with very
little additional complexity -- the patch being about 70 lines of
code), but you don't seem to consider this a good enough argument.
Have I misunderstood something?
> From: Eli Zaretskii <eliz@gnu.org>
> Date: Jan 15, 2019, 11:26 AM
>
> > From: Radon Rosborough <radon.neon@gmail.com>
> > Date: Tue, 15 Jan 2019 11:43:39 -0700
> >
> > > From: Eli Zaretskii <eliz@gnu.org>
> > > Date: Jan 15, 2019, 10:19 AM
> > >
> > > I'm saying that we should hear the complaints first and devise
> > > the solution only after that.
> >
> > If we wait until Emacs 27.2 to fix the complaints, then it will
> > already be too late to do anything useful.
>
> That was the situation before the recent changes, and we still made
> those changes.
I don't see why this would be an argument against the change I am
proposing. The recent changes were useful, which is why we made them,
but they would have been even /more/ useful if we had made them
earlier (before everyone's init-files got changed). The situation is
the same here. Maybe it would still be helpful to make these changes
in Emacs 26.2, but they would be a lot /less/ helpful at that point in
time.
> So maybe the right solution is to make that variable public instead.
Maybe. But this seems like a strictly inferior solution from the
perspective of user experience, since it still results in users being
shown superfluous warnings which waste their time and mental effort.
Best,
Radon
[-- Attachment #2: Type: text/html, Size: 2420 bytes --]
next prev parent reply other threads:[~2019-01-21 22:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 4:17 [PATCH] Only signal package.el warnings when needed Radon Rosborough
2019-01-14 15:48 ` Eli Zaretskii
2019-01-14 16:10 ` Robert Pluim
2019-01-14 16:39 ` Eli Zaretskii
2019-01-14 16:48 ` Robert Pluim
2019-01-14 20:14 ` Stefan Monnier
2019-01-14 21:46 ` Radon Rosborough
2019-01-14 21:46 ` Radon Rosborough
2019-01-15 17:18 ` Eli Zaretskii
2019-01-15 18:43 ` Radon Rosborough
2019-01-15 19:26 ` Eli Zaretskii
2019-01-21 22:45 ` Radon Rosborough [this message]
2019-01-22 17:29 ` Eli Zaretskii
2019-01-23 4:06 ` Radon Rosborough
2019-01-23 15:34 ` Eli Zaretskii
2019-01-23 16:00 ` Stefan Monnier
2019-01-23 17:28 ` Radon Rosborough
2019-01-14 22:13 ` Óscar Fuentes
2019-01-14 22:59 ` Clément Pit-Claudel
2019-01-15 10:39 ` João Távora
2019-01-15 17:15 ` Eli Zaretskii
2019-01-15 17:24 ` João Távora
2019-01-14 19:55 ` Stefan Monnier
2019-01-14 20:19 ` Stefan Monnier
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=CADB4rJEk+cd-LuB6Lce0W6y2_2vtFtULyw9Xwhy9cVZz-GeudA@mail.gmail.com \
--to=radon.neon@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).