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 21:31:27 +0300 [thread overview]
Message-ID: <Z1sr_wvHedXic8o0@lco2> (raw)
In-Reply-To: <871pyd8383.fsf@web.de>
* Michael Heerdegen via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2024-12-12 16:02]:
> Jean Louis <bugs@gnu.support> writes:
>
> > > 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.
>
> That's the global binding. A buffer local binding is reported as "local
> in buffer XYZ" - even when the local binding is the same as the global
> one.
>
> `defvar-local' defines a global (aka "default") value. Until you make an
> assignment in some buffer no buffer local bindings exist.
Okay, I am lost, will review it again when I need it, even though I use heavily permanent-local variables:
(defvar-local rcd-tabulated-original-entries nil
"Original `tabulated-list-entries'.")
(put 'rcd-tabulated-original-entries 'permanent-local t)
But now when I use them, I just use them, I forgot pretty much about
it. It just works in the application.
--
Jean Louis
next prev parent reply other threads:[~2024-12-12 18:31 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
2024-12-12 13:01 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-12 18:31 ` Jean Louis [this message]
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=Z1sr_wvHedXic8o0@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).