PS: to 1b) if custom-file was already loaded, it will be in variable load-history /PA On Wed, 5 Jan 2022 at 08:03, Pedro Andres Aranda Gutierrez < paaguti@gmail.com> wrote: > Let me try to put it another way: as I envisage the whole process > > 1.- On startup: > a) Get the startup file from [ .emacs, .emacs.d/init.el, > .config/emacs/init.el ] or whatever set of files we decide and load it > b) if custom-file is not nil and wasn't already loaded, load custom-file. > If is was already loaded, maybe tell the user (???) > > 2.- When saving the customisations > if custom-file is not nil, save them there else save them in the startup > file whatever it is > > AFAIK, the only new thing is to include 1b) in the emacs code, because 1a) > and 2) are already in the code (it's how emacs behaves today, right?) > > So someone not defining custom-file would not see anything changing > (long-standing behaviour respected) > > Just my .2 cents, /PA > > > On Wed, 5 Jan 2022 at 02:01, Po Lu wrote: > >> Robert Pluim writes: >> >> > Making people who wish to retain long-standing behaviour set a >> > variable or edit a config file for something as fundamental as loading >> > and saving customizations is not something I would want, ever. >> >> Agreed, and I also think that long-standing behaviour should never >> change as well, even for sites that have Emacs freshly installed. >> >> Thanks. >> > > > -- > Fragen sind nicht da um beantwortet zu werden, > Fragen sind da um gestellt zu werden > Georg Kreisler > -- Fragen sind nicht da um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler