unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: carlmarcos--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Generality of defvar
Date: Wed, 27 Jul 2022 01:36:26 +0200 (CEST)	[thread overview]
Message-ID: <N7wraXO--3-2@tutanota.com> (raw)
In-Reply-To: <874jz3sbvm.fsf@dataswamp.org>


Jul 26, 2022, 23:16 by incal@dataswamp.org:

> carlmarcos--- via Users list for the GNU Emacs text editor wrote:
>
>> Have been looking into defvar and noticed the generality of
>> its use
>>
>> (defvar aname t)
>> (defvar bname nil)
>> (defvar cname 1)
>> (defvar dname "text")
>>
>
> For practical reasons it can be better to do
>
> (defvar var-name)
> (setq var-name 'var-value)
>
> instead because if you do something with that and want to
> reset it, it's enough to evaluate the second line, whereas if
> you just have the first line you tend to evaluate that one and
> if/because the variable is already set at that point then
> nothing will happen ...
>

I cannot follow what you are trying to say.



  parent reply	other threads:[~2022-07-26 23:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 20:35 Generality of defvar carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-26 23:01 ` Philip Kaludercic
     [not found] ` <87r127h40s.fsf@posteo.net-N7wjq17--3-2>
2022-07-26 23:10   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-27  7:29     ` Thibaut Verron
     [not found]     ` <CAFsi02SEVCEjGNoQ6vPZvMw7d5F39JZAAPCR5VOUnzQDUERkQA@mail.gmail.com-N7yZ2U2----2>
2022-07-27 12:18       ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-27 12:34         ` Emanuel Berg
2022-07-27 12:52           ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-27 13:21             ` Thibaut Verron
2022-07-27 13:24               ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-27 13:47                 ` Thibaut Verron
2022-07-27 16:29                   ` Christopher Dimech
2022-07-27 16:39                     ` Thibaut Verron
2022-07-28  6:42                       ` Christopher Dimech
2022-07-28  7:06                         ` Thibaut Verron
2022-07-28  7:34                           ` Christopher Dimech
2022-07-28  9:37                             ` thibaut.verron
2022-07-28 13:57                               ` Christopher Dimech
2022-07-26 23:16 ` Emanuel Berg
2022-07-26 23:23   ` Emanuel Berg
2022-07-26 23:36   ` carlmarcos--- via Users list for the GNU Emacs text editor [this message]
2022-07-27  4:57   ` Yuri Khan
2022-07-27  6:59     ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-29 15:56     ` Emanuel Berg
2022-07-29 16:25       ` [External] : " Drew Adams
2022-07-30  3:56         ` Emanuel Berg
2022-07-30 19:36           ` Drew Adams
2022-08-01  3:24             ` Emanuel Berg

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=N7wraXO--3-2@tutanota.com \
    --to=help-gnu-emacs@gnu.org \
    --cc=carlmarcos@tutanota.com \
    --cc=incal@dataswamp.org \
    /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).