From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: One-off history for read-string
Date: Sat, 26 Sep 2015 04:02:47 +0200 [thread overview]
Message-ID: <87zj0arl88.fsf@debian.uxu> (raw)
In-Reply-To: 87oagrt1d0.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
> However, I don't care about /writing/ it to some
> variable in Emacs, since the new entry will be
> uploaded to the server anyway, and taken from there
> the next time, together with the rest of
> the history.
So then, what does it matter?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-09-26 2:02 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
2015-09-25 7:16 ` Marcin Borkowski
2015-09-26 2:02 ` Emanuel Berg [this message]
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=87zj0arl88.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.
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).