From: Pankaj Jangid <pankaj@codeisgreat.org>
To: help-gnu-emacs@gnu.org
Subject: Re: difference between setq and setq-local
Date: Tue, 28 Sep 2021 08:32:50 +0530 [thread overview]
Message-ID: <87fstpjtb9.fsf@codeisgreat.org> (raw)
In-Reply-To: 87sfxqr95n.fsf@zoho.eu
Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> So setq-local always does the same thing.
>
> And setq-default always does the same thing as well.
>
> setq tho is the tricky one, it refers to the buffer-local
> variable if it exists ... _or_ acts like `setq-local' for some
> specific variables ... _or_ acts like setq-default if the
> there isn't buffer-local variable and also the variable
> doesn't stipulate it wants to be buffer-local soo bad!
Thanks for this primer on ‘setq-’ functions. It is permanently inscribed
now. And it is absolutely clear.
prev parent reply other threads:[~2021-09-28 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 3:03 difference between setq and setq-local Pankaj Jangid
2021-09-27 3:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 3:02 ` Pankaj Jangid [this message]
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=87fstpjtb9.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.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).