From: Alex Kost <alezost@gmail.com>
To: Perry Smith <pedzsan@gmail.com>
Cc: "help-gnu-emacs@gnu.org Help" <help-gnu-emacs@gnu.org>
Subject: Re: Help needed with defadvice
Date: Sat, 23 Nov 2013 11:00:26 +0400 [thread overview]
Message-ID: <878uwf4n79.fsf@gmail.com> (raw)
In-Reply-To: <FD742D45-BCB4-48BD-A915-C152D2089A6D@gmail.com> (Perry Smith's message of "Fri, 22 Nov 2013 19:41:29 -0600")
Perry Smith (2013-11-23 05:41 +0400) wrote:
> Thanks... I attacked this from the opposite direction adding debug trying to narrow down when the locals got killed. I finally bumped into these lines:
>
> (defmacro define-derived-mode (child parent name &optional docstring &rest body)
> ...
> (interactive)
> ; Run the parent.
> (delay-mode-hooks
>
> (,(or parent 'kill-all-local-variables)) <<<<<<<<<
> ; Identify the child mode.
> (setq major-mode (quote ,child))
> (setq mode-name ,name)
> ...)
>
> I'm going to drive home and play with this some more but I predict that that is what is killing my local variables.
>
> Does anyone know why this is there?
>
> I somewhat assumed I had this in some of my poop but this is stock emacs code (24.3).
As for me, i don't see a reason for killing local variables there. For
example i have some local variables and after "M-x text-mode" they all
die as text-mode is a derived-mode. This behaviour doesn't seem right
to me.
Will you "M-x report-emacs-bug" about it? (to clarify why that is there)
next prev parent reply other threads:[~2013-11-23 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 2:45 Help needed with defadvice Perry Smith
2013-11-22 6:27 ` Eric Abrahamsen
2013-11-22 7:09 ` Alex Kost
2013-11-22 15:50 ` Perry Smith
2013-11-22 21:56 ` Alex Kost
2013-11-23 1:41 ` Perry Smith
2013-11-23 7:00 ` Alex Kost [this message]
2013-11-23 14:48 ` Stefan Monnier
2013-11-23 15:22 ` Perry Smith
2013-11-23 15:38 ` Stefan Monnier
2013-11-23 16:24 ` Perry Smith
2013-11-24 18:21 ` Stefan Monnier
2013-11-23 15:43 ` Alex Kost
[not found] ` <mailman.6834.1385135422.10748.help-gnu-emacs@gnu.org>
2013-11-23 8:35 ` jack-mac
2013-11-22 14:44 ` Stefan Monnier
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=878uwf4n79.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pedzsan@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.
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).