all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "xenodasein@tutanota.de" <xenodasein@tutanota.de>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Have Customize always use `custom-file`
Date: Mon, 3 Jan 2022 16:28:48 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488A5BD5277285244D2A145F3499@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <MsVjWIe--N-2@tutanota.de>

> > The only real change is to prevent Customize
> > from writing to your init file.  Nothing else.
> 
> I am fine with this behavior, as long as we can 
> place the (load custom-file) anywhere we want.

That's absolutely the idea.

> https://urldefense.com/v3/__https://stackoverflow.com/questions/32693757/ema
> cs-package-customization-and-autoloads__;!!ACWV5N9M2RV99hQ!c2-
> NuVQ8MqOxWafY1oZFpAqa4eJ48VUOtqgkFN5MBhM5OaDEMLrRnnTkujdhwFe1$

I answered that question at that location, in 2015:

https://stackoverflow.com/a/32697325/729907

  reply	other threads:[~2022-01-03 16:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 16:15 Have Customize always use `custom-file` Drew Adams
2022-01-03 16:20 ` xenodasein--- via Emacs development discussions.
2022-01-03 16:28   ` Drew Adams [this message]
2022-01-03 17:02     ` [External] : " xenodasein--- via Emacs development discussions.
2022-01-04  1:00       ` Po Lu
2022-01-04  9:41         ` xenodasein--- via Emacs development discussions.
2022-01-04  9:48           ` Po Lu
2022-01-04 10:29             ` xenodasein--- via Emacs development discussions.
2022-01-04 10:33               ` Po Lu
2022-01-04 10:44                 ` xenodasein--- via Emacs development discussions.
2022-01-04 10:53                   ` Po Lu
2022-01-05  3:54               ` Richard Stallman
2022-01-05  5:35                 ` tomas
2022-01-06  3:57                   ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488A5BD5277285244D2A145F3499@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=xenodasein@tutanota.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.