From: Marcin Borkowski <mbork@mbork.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: One-off history for read-string
Date: Thu, 24 Sep 2015 18:27:27 +0200 [thread overview]
Message-ID: <87wpvfu6j4.fsf@mbork.pl> (raw)
In-Reply-To: <jwveghn2542.fsf-monnier+gmane.emacs.help@gnu.org>
On 2015-09-24, at 17:47, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Is it fine to use a temporary, let-bound variable name as the HISTORY
>> parameter, or is there a better way for a "history" I only need to read
>> from, not to write to?
>
> It's probably OK, but do declare this variable with (defvar <myvar>)
> since it shouldn't be lexically bound
Ah, I don't use lexical binding in my package. I probably should;
thanks for this advice!
> Note also that if the user uses nested minibuffers, she may have two
> such commands active at the same time, so you may need to generate the
> symbol dynamically rather than always use the same symbol.
Rather not applicable to my situation. But out of curiosity: what are
"nested minibuffers" and where can I read about them? In my Emacs, when
I try to issue a command which needs minibuffer while I'm in
a minibuffer, I get the message "Command attempted to use minibuffer
while in minibuffer".
> Stefan
Thanks,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-09-24 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 12:10 One-off history for read-string Marcin Borkowski
2015-09-24 15:47 ` Stefan Monnier
2015-09-24 16:27 ` Marcin Borkowski [this message]
2015-09-24 17:04 ` Drew Adams
2015-09-25 0:34 ` Emanuel Berg
2015-09-25 7:16 ` Marcin Borkowski
2015-09-26 2:02 ` Emanuel Berg
2015-09-26 2:33 ` John Mastro
2015-09-26 2:47 ` Emanuel Berg
2015-09-26 7:46 ` Marcin Borkowski
2015-09-27 1:20 ` Emanuel Berg
2015-09-27 6:02 ` Marcin Borkowski
2015-09-27 23:14 ` Emanuel Berg
2015-09-28 0:50 ` Stefan Monnier
2015-09-26 7:46 ` Marcin Borkowski
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=87wpvfu6j4.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.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.
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).