unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Nick Andryshak <nandryshak@gmail.com>,
	Alan Morgan <Alan.Morgan@nextlabs.com>
Cc: 20521@debbugs.gnu.org
Subject: bug#20521: Bug 2051
Date: Fri, 15 May 2015 14:42:22 -0700 (PDT)	[thread overview]
Message-ID: <19f6a4a4-81d6-499f-9f90-d41a1dda9c4c@default> (raw)
In-Reply-To: <oiry4kpczw9.fsf@gmail.com>

> I think you may misunderstand: setq always sets a global variable.

Since when?

  -- Macro: setq-local variable value
     This macro creates a buffer-local binding in the current buffer for
     VARIABLE, and gives it the buffer-local value VALUE.  It is
     equivalent to calling `make-local-variable' followed by `setq'.
     VARIABLE should be an unquoted symbol.

Note the last sentence, which points out that `setq' does not always
set a global variable.  If it did, then so would `setq-local',
according to that text.





  reply	other threads:[~2015-05-15 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 23:35 bug#20521: Viper version is 3.14.2 of July 4, 2013; After some hours of use I don't enter viper mode automatically on new files Alan Morgan
2015-05-15 20:39 ` bug#20521: Bug 2051 Alan Morgan
2015-05-15 21:08   ` Nick Andryshak
2015-05-15 21:42     ` Drew Adams [this message]
2015-05-15 23:24       ` Nick Andryshak
2015-05-15 21:51     ` Alan Morgan
2015-05-27 16:50 ` bug#20521: setq-local definitely behaving oddly for viper mode Alan Morgan
2015-05-27 22:28   ` Johan Bockgård
2015-05-28  2:02     ` Stefan Monnier
2022-02-10  8:11     ` bug#20521: Viper version is 3.14.2 of July 4, 2013; After some hours of use I don't enter viper mode automatically on new files Lars Ingebrigtsen

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=19f6a4a4-81d6-499f-9f90-d41a1dda9c4c@default \
    --to=drew.adams@oracle.com \
    --cc=20521@debbugs.gnu.org \
    --cc=Alan.Morgan@nextlabs.com \
    --cc=nandryshak@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).