unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why does saving a buffer to a new file clear local variables?
Date: Thu, 12 Dec 2024 15:41:57 +0300	[thread overview]
Message-ID: <Z1raFSZAi4vLAfFp@lco2> (raw)
In-Reply-To: <87bjxh87cr.fsf@web.de>

* Michael Heerdegen via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2024-12-12 14:33]:
> Jean Louis <bugs@gnu.support> writes:
> 
> > I have just checked it, try doing it this way:
> >
> > (defvar-local abc 123)
> >
> > save the buffer, and verify the abc is still there.
> 
> Are you sure that you don't just see the global binding of that
> variable?

Unless you wish to reveal some new fact about it to me, I see that by
using `defvar-local' I can save file and variable `abc' still has
initially assigned value.

And it has this description:

abc’s value is 123

Not documented as a variable.

  Automatically becomes buffer-local when set.

> > This way, it doesn't work, variable must be symbol, not string:
> > (make-variable-buffer-local "abc")
> 
> Please note that `make-variable-buffer-local' is a function (in contrast
> to `defvar' or `defvar-local' which are macros), so the argument
> (expression) is evaluated and should return a symbol.  When you want to
> specify a symbol quote its name: 'SYMBOL.

That is for original poster. I also said that way it would not work.

-- 
Jean Louis



  reply	other threads:[~2024-12-12 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  4:05 Why does saving a buffer to a new file clear local variables? Patrick Nicodemus
2024-12-12  7:31 ` Jean Louis
2024-12-12 11:32   ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-12 12:41     ` Jean Louis [this message]
2024-12-12 13:01       ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-12 18:31         ` Jean Louis
2024-12-12 12:50 ` Michael Heerdegen

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=Z1raFSZAi4vLAfFp@lco2 \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).