From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: One-off history for read-string
Date: Fri, 25 Sep 2015 02:34:50 +0200 [thread overview]
Message-ID: <87twqjpc9h.fsf@debian.uxu> (raw)
In-Reply-To: 87y4fwt3vq.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
> (I'm working on a client for certain web service,
> and the history is kept on the server, so it really
> doesn't make sense to keep all those in my
> Emacs session.)
Perhaps not (?), but why think of this at all?
What problem is it, that you experience, or what
behavior do you seek?
> 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?
If you consider the prototype
(read-string PROMPT &optional INITIAL-INPUT HISTORY
DEFAULT-VALUE INHERIT-INPUT-METHOD)
you see that the HISTORY argument is optional - you
don't need to have anything there, and if you want to
pass something to subsequent optional arguments, pass
nil as HISTORY.
You can see an example of using `read-string' like
this here:
http://user.it.uu.se/~embe8573/conf/emacs-init/w3m/w3m-unisearch.el
on line 116.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-09-25 0:34 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
2015-09-24 17:04 ` Drew Adams
2015-09-25 0:34 ` Emanuel Berg [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twqjpc9h.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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.
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.