From: Alan Mackenzie <acm@muc.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: How do I tell when the current buffer is the minibuffer?
Date: Sat, 5 Mar 2016 22:19:14 +0000 [thread overview]
Message-ID: <20160305221914.GB26757@acm.fritz.box> (raw)
In-Reply-To: <87lh5w37jq.fsf@linux-m68k.org>
Hello, Andreas.
On Sat, Mar 05, 2016 at 11:04:57PM +0100, Andreas Schwab wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > Part of my program is being called from `signal_after_change' after
> > activity in the minibuffer. However, in that program the buffer local
> > variables for the main buffer (not the minibuffer) are still in scope.
> How can that happen? A minibuffer is a buffer on its own, with its own
> local variables.
What is happening is that the variable location (created in C) is being
shared by all buffers until a buffer local value is "primed" in a buffer
with a `setq' invocation.
How does one correctly create a buffer local variable in C? What I have
at the moment is:
DEFSYM (Qcomment_depth_hwm, "comment-depth-hwm");
DEFVAR_LISP ("comment-depth-hwm", Vcomment_depth_hwm,
doc: /* Buffer position below which the `comment-depth' property is valid. */);
Vcomment_depth_hwm = make_number (1);
Fmake_variable_buffer_local (Qcomment_depth_hwm);
This is clearly inadequate, of itself, to create a buffer local variable.
> Andreas.
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-03-05 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 21:02 How do I tell when the current buffer is the minibuffer? Alan Mackenzie
2016-03-05 21:39 ` raman
2016-03-05 22:04 ` Andreas Schwab
2016-03-05 22:19 ` Alan Mackenzie [this message]
2016-03-05 22:40 ` Andreas Schwab
2016-03-05 22:51 ` Alan Mackenzie
2016-03-05 23:03 ` Andreas Schwab
2016-03-05 23:20 ` Alan Mackenzie
2016-03-06 17:44 ` Eli Zaretskii
2016-03-06 21:44 ` Alan Mackenzie
2016-03-08 5:00 ` Stefan Monnier
2016-03-06 20:15 ` Johan Bockgård
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=20160305221914.GB26757@acm.fritz.box \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.
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.