unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is there a way of setting a variable only when it exists?
Date: Tue, 15 Mar 2022 07:17:42 +0100	[thread overview]
Message-ID: <87a6drviwp.fsf@mbork.pl> (raw)
In-Reply-To: <878rtcir1h.fsf@zoho.eu>


On 2022-03-14, at 14:48, Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:

> Stefan Monnier via Users list for the GNU Emacs text editor wrote:
>
>>> I assume it would be fairly easy to code such a macro
>>> (using `boundp'), but maybe it exists already?
>>
>> AFAIK it doesn't exist yet. The reason for it is that it is
>> not often useful. Typically there are two cases:
>>
>> - If the var exist, you want to set it and if not you have
>>   no fallback. In that case, it is typically harmless to set
>>   the var even when it doesn't exist, so the code just uses
>>   `setq` without bothering to test `boundp`.
>>
>> - If the var exist you want to set it, and if it doesn't you
>>   want to do something else. In that case, the something
>>   else tends to depend on the specifics so (if (boundp 'foo)
>>   (setq foo ..) ...) is about s good as it gets.
>
> If it exists set it with `setq'. If it doesn't exist, create
> and set it ... with `setq'?

What if it's an internal Emacs variable which might become a user option
one day (I submitted a bug report about it) and then my customization
silently disappears?  It's the "silently" part I want to guard
against...

Best,

-- 
Marcin Borkowski
http://mbork.pl



  reply	other threads:[~2022-03-15  6:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14  6:00 Is there a way of setting a variable only when it exists? Marcin Borkowski
2022-03-14 12:52 ` Eli Zaretskii
2022-03-14 13:16 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-14 13:48   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15  6:17     ` Marcin Borkowski [this message]
2022-03-15  6:50       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15  6:58       ` Jean Louis
2022-03-15  7:45         ` Marcin Borkowski
2022-03-15  8:12           ` Jean Louis
2022-03-15  7:49         ` tomas
2022-03-15  8:13           ` Jean Louis
2022-03-15  8:36             ` tomas
2022-03-15  9:28               ` Jean Louis
2022-03-15 10:01                 ` tomas
2022-03-15 11:29                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15  8:14           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 15:33         ` [External] : " Drew Adams
2022-03-15 15:38       ` Drew Adams
2022-03-16 18:32         ` Marcin Borkowski
2022-03-16  0:47       ` Michael Heerdegen
2022-03-16 18:33         ` Marcin Borkowski
2022-03-16  6:02       ` Tomas Nordin
2022-03-16  6:37         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16 18:34         ` Marcin Borkowski
2022-03-15  6:48     ` Jean Louis
2022-03-14 22:09 ` Michael Heerdegen
2022-03-15  6:16   ` Marcin Borkowski
2022-03-15  7:05     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16  0:25     ` Michael Heerdegen
2022-03-16 18:33       ` Marcin Borkowski
2022-03-16 19:25         ` Michael Heerdegen
2022-03-18  5:58           ` Marcin Borkowski
2022-03-16 20:35         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-17 20:47           ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-18  5:59             ` Marcin Borkowski
2022-03-18 17:59           ` Jean Louis
2022-03-19  9:25             ` 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=87a6drviwp.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --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).