unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: package-update-all from command line
Date: Wed, 25 May 2022 11:14:19 -0400	[thread overview]
Message-ID: <lzleupk5kk.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <jwvilpun2gq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 24 May 2022 15:55:41 -0400")

> * Stefan Monnier <zbaavre@veb.hzbagerny.pn> [2022-05-24 15:55:41 -0400]:
>
> Ah, that might be it.  Indeed the quickstart file contains:
>
>           `(setq package-activated-list
>                  (append ',(mapcar #'package-desc-name package--quickstart-pkgs)
>                          package-activated-list))
>
> :-(
>
>> One is not supposed to do that, of course...
>
> If it happens accidentally, please report it as a bug.

WDYM "accidentally"?
At any rate, I think replacing `append' with `cl-union' (or equivalent)
in the code above would be a good idea.

>>> `package-archives` is a completely different problem because it's
>>> a defcustom which may be set to a different value in the user's config
>>> in all kinds of different ways, and which may be eval'd either before or
>>> after loading the quickstart file, so it *would* mess up the user's
>>> config in various circumstances.
>> so save a new non-user variable like `package-current-archives' instead,
>> so that I can set `package-archives' from it on the command line.
>
> Setting `package-archives` from `package-current-archives` doesn't seem
> much easier than the ad-hoc addition of "melpa" you're currently using,
> so it doesn't seem like a great improvement.

It helps me maintain my additions to `package-archives' in _one_ place
(.emacs) instead of 2 places (.emacs + the command line).

>>> Maybe a more general way to attack this problem would be to try and
>>> create a "quickinit.el" file which is a bit like a "dump" of the user's
>>> config, so it can be used instead of loading `init.el`?
>> here we already have package-quickstart.el which can be re-used.
>
> AFAIK the problem is not how to name the file but what to put into it.

I am not talking about naming, but rather reusing an existing file for a
related purpose.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2113
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://thereligionofpeace.com https://www.dhimmitude.org
Beliefs divide, doubts unite.



  reply	other threads:[~2022-05-25 15:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  3:42 package-update-all from command line Sam Steingold
2022-05-24 13:54 ` Stefan Monnier
2022-05-24 14:05   ` Eli Zaretskii
2022-05-24 16:00     ` Loading early-init.el in batch mode (was: package-update-all from command line) Stefan Monnier
2022-05-24 18:58       ` Eli Zaretskii
2022-05-24 15:04   ` package-update-all from command line Sam Steingold
2022-05-24 15:52     ` Stefan Monnier
2022-05-24 19:01       ` Sam Steingold
2022-05-24 19:55         ` Stefan Monnier
2022-05-25 15:14           ` Sam Steingold [this message]
2022-05-25 16:13             ` Stefan Monnier
2022-05-26 15:13               ` Sam Steingold
2022-05-26 15:35                 ` Stefan Monnier
2022-05-25  1:26 ` Lars Ingebrigtsen
2022-05-25  4:58   ` Tassilo Horn
2022-05-25 12:05     ` Lars Ingebrigtsen
2022-05-25 12:27       ` Tassilo Horn
2022-05-27 10:21         ` Lars Ingebrigtsen
2022-05-27 20:33           ` Tassilo Horn

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=lzleupk5kk.fsf@3c22fb11fdab.ant.amazon.com \
    --to=sds@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).