From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Morgan <Alan.Morgan@nextlabs.com>,
"20521@debbugs.gnu.org" <20521@debbugs.gnu.org>
Subject: 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
Date: Thu, 10 Feb 2022 09:11:57 +0100 [thread overview]
Message-ID: <87h797b0oi.fsf_-_@gnus.org> (raw)
In-Reply-To: <87zj4pirjb.fsf@gnu.org> ("Johan Bockgård"'s message of "Thu, 28 May 2015 00:28:40 +0200")
Johan Bockgård <bojohan@gnu.org> writes:
> Apparently even an explicit setq-local (make-local-variable) cannot
> create a local binding in the situation that the second paragraph talks
> about:
>
> (progn
> (make-variable-buffer-local 'x)
> (let ((x 0))
> (setq-local x 1)
> (cons (local-variable-p 'x)
> (default-value 'x))))
> => (nil . 1)
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
It looks like this has been fixed in the years since it was reported --
this form evaluates to (t) in Emacs 29, so I'm closing this bug report.
If there's more to be done here, please respond to the debbugs address
and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-10 8:11 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
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 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h797b0oi.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=20521@debbugs.gnu.org \
--cc=Alan.Morgan@nextlabs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.