unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: User setup for emacs
Date: Mon, 11 Oct 2021 16:30:25 +0000	[thread overview]
Message-ID: <SJ0PR10MB54885B2194C7795A25D01F59F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87r1cr1ql2.fsf@zoho.eu>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

>> just don't use Customize - either its UI or its
>> functions (those that save settings).
>
> I never use the UI, as for the functions ... hm, okay, these
> are the hits a get in my Elisp on "custom". Do you
> anything fishy?

The functions that write to a file have both
`custom' and `save' in their names.  But you
might invoke some other function that in turn
calls one of those.  Here are those I see:

custom-face-save
custom-group-save
custom-reset-standard-save-and-update
custom-save-all
custom-save-faces
custom-save-variables
custom-theme-save
custom-variable-save
customize-push-and-save
customize-save-customized
customize-save-variable

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 13978 bytes --]

  parent reply	other threads:[~2021-10-11 16:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 15:30 User setup for emacs tolugboji via Users list for the GNU Emacs text editor
2021-10-08 16:16 ` tolugboji
2021-10-09 10:03   ` tolugboji
2021-10-10 14:19     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 14:33       ` tolugboji
2021-10-10 15:41         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 15:47           ` tolugboji
2021-10-10 16:45             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 17:11               ` tolugboji
2021-10-11  0:04                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11  1:23                   ` tolugboji
2021-10-11  3:09                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 18:00 ` Eduardo Ochs
2021-10-10 18:14   ` tolugboji
2021-10-10 18:31   ` [External] : " Drew Adams
2021-10-10 18:35     ` tolugboji
2021-10-10 19:02       ` [External] : " Drew Adams
2021-10-10 19:11         ` tolugboji
2021-10-11  0:02           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 23:59     ` [External] : " Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11  0:34       ` Drew Adams
2021-10-11  3:13         ` Emanuel Berg via Users list for the GNU Emacs text editor
     [not found]           ` <SJ0PR10MB5488088380C0302344DA8E15F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]             ` <87r1cr1ql2.fsf@zoho.eu>
2021-10-11 16:30               ` Drew Adams [this message]
2021-10-11 16:38                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 16:39                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 16:43                   ` Emanuel Berg via Users list for the GNU Emacs text editor

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=SJ0PR10MB54885B2194C7795A25D01F59F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.
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).