GNU bug report logs - #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

Previous Next

Full log

View this message in rfc822 format

From: Nick Andryshak <nandryshak <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Alan Morgan <Alan.Morgan <at> nextlabs.com>, 20521 <at> debbugs.gnu.org
Subject: bug#20521: Bug 2051
Date: Fri, 15 May 2015 19:24:38 -0400

[Message part 1 (text/plain, inline)]

Interesting, thanks. I suppose I misunderstand the manual page that I
linked.

- Nick

On Fri, May 15, 2015 at 5:42 PM, Drew Adams <drew.adams <at> oracle.com> wrote:

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

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.