From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Does defvar-local has same effect as make-variable-buffer-local?
Date: Sun, 16 May 2021 07:11:29 +0300 [thread overview]
Message-ID: <838s4fwc5q.fsf@gnu.org> (raw)
In-Reply-To: <courier.0000000060A02BB5.00006B30@stw1.rcdrun.com> (message from Jean Louis on Sat, 15 May 2021 23:14:38 +0300)
> Date: Sat, 15 May 2021 23:14:38 +0300
> From: Jean Louis <bugs@gnu.support>
>
> I did read the documentation, yet I need assurance on this subject.
Why not look at the source? Then you could be absolutely sure.
next prev parent reply other threads:[~2021-05-16 4:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 20:14 Does defvar-local has same effect as make-variable-buffer-local? Jean Louis
2021-05-15 20:49 ` [External] : " Drew Adams
2021-05-15 21:01 ` Drew Adams
2021-05-15 21:41 ` Jean Louis
2021-05-15 22:16 ` Drew Adams
2021-05-15 22:21 ` Jean Louis
2021-05-16 4:11 ` Eli Zaretskii [this message]
2021-05-16 8:09 ` Jean Louis
2021-05-16 8:52 ` Yuri Khan
2021-05-16 16:53 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-16 8:55 ` Eli Zaretskii
2021-05-16 11:26 ` Jean Louis
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=838s4fwc5q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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).