From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Clément Pit-Claudel" <cpitclaudel@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] Only signal package.el warnings when needed
Date: Tue, 15 Jan 2019 17:24:58 +0000 [thread overview]
Message-ID: <CALDnm53pzv+sM0VTyAwrAFEbsE6DV7s__HuO6gmiUKW3GX+q-A@mail.gmail.com> (raw)
In-Reply-To: <834la9etai.fsf@gnu.org>
On Tue, Jan 15, 2019 at 5:15 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: João Távora <joaotavora@gmail.com>
> > Date: Tue, 15 Jan 2019 10:39:16 +0000
> > Cc: emacs-devel <emacs-devel@gnu.org>
> >
> > On Mon, Jan 14, 2019, 23:37 Clément Pit-Claudel <cpitclaudel@gmail.com wrote:
> >
> > On 14/01/2019 17.13, Óscar Fuentes wrote:
> > > Not to mention the noise it creates for those of us that occasionally
> > > work with multiple Emacs versions and the same init files.
> >
> > This is my main source of annoyance with the warning, thought that annoyance did not raise to the level
> > of complaining about it in public until now :)
> >
> > Ditto :)
>
> I'm questioning the wisdom of adding non-trivial complexity on account
> of annoyances that "did not raise to the level of complaining about it
> in public". Shouldn't we collect more experience regarding the
> current solution before we complicate it more?
That makes sense too. To be honest, I have a commented out
definition of (package-initialize) in my init which works for me.
When I switch to Emacs 26.1 I remember to M-x package-initialize
and that solves it for me (because I don't use package.el much).
João Távora
next prev parent reply other threads:[~2019-01-15 17:24 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
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 [this message]
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=CALDnm53pzv+sM0VTyAwrAFEbsE6DV7s__HuO6gmiUKW3GX+q-A@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=cpitclaudel@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).