From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Comments on setopt
Date: Tue, 15 Feb 2022 17:20:22 +0000 [thread overview]
Message-ID: <878rucnj1l.fsf@posteo.net> (raw)
In-Reply-To: <jwv8rucff46.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 15 Feb 2022 08:15:10 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> - While I don't mind it really, I can imagine that others might object
>>> to the "long" name, when compared to setq. Would a default alias like
>>> "seto" or "setc" be worth it or not?
>> I think `seto' is confusing, and `setc' doesn't really tell you
>> anything. The salient thing is that we're setting user option, not that
>> it's been defined by `defcustom'.
>
> FWIW, it took me a while to understand what "long name" Philip was
> talking about because I assumed `setopt` wouldn't be considered as
> long. ;-)
The only reason I bring this up is that if someone has a block like
(setq save-interprogram-paste-before-kill t
kill-do-not-save-duplicates t
mouse-yank-at-point t)
they might hesitate to use setopt, purely because of the aesthetic
disadvantage of now being indented more:
(setopt save-interprogram-paste-before-kill t
kill-do-not-save-duplicates t
mouse-yank-at-point t)
Again, nothing critical (one could also start listing option in the
second line), but something I could anticipate being brought up..
>
> Stefan
>
--
Philip Kaludercic
next prev parent reply other threads:[~2022-02-15 17:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 23:01 Comments on setopt Philip Kaludercic
2022-02-15 3:40 ` Po Lu
2022-02-16 4:12 ` Richard Stallman
2022-02-16 7:04 ` Rudolf Adamkovič
2022-02-16 9:52 ` Phil Sainty
2022-02-16 13:23 ` Stefan Monnier
2022-02-16 22:34 ` Phil Sainty
2022-02-16 22:42 ` Stefan Monnier
2022-02-16 22:57 ` Philip Kaludercic
2022-02-16 7:13 ` Po Lu
2022-02-19 4:54 ` Richard Stallman
2022-02-19 5:07 ` Po Lu
2022-02-19 8:47 ` Eli Zaretskii
2022-02-19 11:13 ` Lars Ingebrigtsen
2022-02-19 11:52 ` Mathias Dahl
2022-02-19 12:35 ` Dmitry Gutov
2022-02-19 14:41 ` Name for `setopt` (was: Comments on setopt) Stefan Monnier
2022-02-19 18:31 ` Comments on setopt Philip Kaludercic
2022-02-19 23:42 ` [External] : " Drew Adams
2022-02-15 9:32 ` Lars Ingebrigtsen
2022-02-15 13:15 ` Stefan Monnier
2022-02-15 17:20 ` Philip Kaludercic [this message]
2022-02-17 11:27 ` Lars Ingebrigtsen
2022-02-15 17:17 ` Philip Kaludercic
2022-02-15 19:22 ` Juri Linkov
2022-02-17 11:28 ` 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=878rucnj1l.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).