[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Comments on setopt
From: |
Po Lu |
Subject: |
Re: Comments on setopt |
Date: |
Tue, 15 Feb 2022 11:40:32 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Philip Kaludercic <philipk@posteo.net> writes:
> Hi Lars,
>
> I'm glad to see the recent addition of the setopt macro.
Indeed, it's a great addition.
> - 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 setopt is enough. "seto" might be confused with oset, while I
don't immediately see what "setc" is supposed to represent.
What I find problematic is the large scale replacement of
`custom-set-variables' with setopt in the user manual. I think there
was once a specific reason to use `custom-set-variables' there, but I
can't remember what.
- Comments on setopt, Philip Kaludercic, 2022/02/14
- Re: Comments on setopt,
Po Lu <=
- Re: Comments on setopt, Richard Stallman, 2022/02/15
- Re: Comments on setopt, Rudolf Adamkovič, 2022/02/16
- Re: Comments on setopt, Phil Sainty, 2022/02/16
- Re: Comments on setopt, Stefan Monnier, 2022/02/16
- Re: Comments on setopt, Phil Sainty, 2022/02/16
- Re: Comments on setopt, Stefan Monnier, 2022/02/16
- Re: Comments on setopt, Philip Kaludercic, 2022/02/16
- Re: Comments on setopt, Po Lu, 2022/02/16
- Re: Comments on setopt, Richard Stallman, 2022/02/18
- Re: Comments on setopt, Po Lu, 2022/02/19