From: Stefan Kangas <stefankangas@gmail.com>
To: uzibalqa <uzibalqa@proton.me>, 57847@debbugs.gnu.org
Subject: bug#57847: Emacs Reference Lisp Manual on defcustom
Date: Fri, 16 Sep 2022 03:00:56 -0700 [thread overview]
Message-ID: <CADwFkm=_jENNpDv0fLzH9jko2gNX4bLxDfpRNf2BAnOLfo=GaA@mail.gmail.com> (raw)
In-Reply-To: <YVjmAM0utJUVNmU9-oawjuRA_okdddXPmK5Qx9kfPta2OSQ2CdpJKX4yp-b5ol__AzDBfbbH928Jvqe-T6yjgTIGoKRl_wH4hjAmVdNR-r8=@proton.me>
severity 57847 wishlist
thanks
uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> I am reading the Elisp manual
This is from An Introduction to Programming in Emacs Lisp:
(info "(eintr) defcustom")
> 16.2 Specifying Variables using defcustom
>
> The custom-set-variables function works somewhat differently than a setq. While I have never learned the differences, I modify the custom-set-variables expressions in my .emacs file by hand: I make the changes in what appears to me to be a reasonable manner and have not had any problems. Others prefer to use the Customization command and let Emacs do the work for them.
>
> I myself use customize for hardly anything. Mostly, I write expressions myself.
>
> Why are we talking like this !!! "I have never learned the differences" and "I myself use customize for hardly anything."
That's just the style that this manual is written in. Maybe we could
explain what `custom-set-*' actually does instead, or even mention the
new `setopt'. Or we could just leave it alone: either way is fine by
me.
next prev parent reply other threads:[~2022-09-16 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 4:31 bug#57847: Emacs Reference Lisp Manual on defcustom uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-16 10:00 ` Stefan Kangas [this message]
2022-09-16 10:05 ` Lars Ingebrigtsen
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='CADwFkm=_jENNpDv0fLzH9jko2gNX4bLxDfpRNf2BAnOLfo=GaA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=57847@debbugs.gnu.org \
--cc=uzibalqa@proton.me \
/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).