From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 7567@debbugs.gnu.org
Subject: bug#7567: Please add a history variable to read-regexp
Date: Mon, 6 Dec 2010 15:11:53 -0800 [thread overview]
Message-ID: <DF06262AA19C4341B1B745D93DC6ABA0@us.oracle.com> (raw)
In-Reply-To: <AANLkTimvyK-BnRLOzaBXB9Hwiqo-j24Z=AcF6Yaj=koH@mail.gmail.com>
> Thanks for asking, I thought it was clear.
You're welcome.
> Why should that regexp be used to make buffer names? It is probably a
> regexp that has been used for matching strings in buffers.
Why is it "probably" that?
I use regexps interactively all over the place. Matching text in a buffer is
only one use.
> (It might of course be a regexp from a search in *Buffer List*,
> but that is not the normal case.)
IMO, there is no "normal" case.
This is a general limitation wrt history vars. But it cannot really be
otherwise. You might want some particular values to be available on a given
history list in some context, and you (or I) might want them to not be available
on that list in another context.
We can add more history vars to get finer-grained control, but then you miss out
if you want to access something that it was decided should be on another history
list.
It's impossible to have it both ways, because the user's intention is a variable
that cannot easily and always be taken into consideration. IOW, there are some
things the programmer can decide when writing the function call that reads input
(you can use any history var you want, including new ones), but still you cannot
always know what the user really needs/wants.
next prev parent reply other threads:[~2010-12-06 23:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 2:24 bug#7567: Please add a history variable to read-regexp Lennart Borgman
2010-12-06 22:43 ` Lennart Borgman
2010-12-06 22:57 ` Drew Adams
2010-12-06 23:00 ` Lennart Borgman
2010-12-06 23:11 ` Drew Adams [this message]
2010-12-06 23:23 ` Lennart Borgman
2010-12-07 0:31 ` Drew Adams
2010-12-07 4:09 ` Drew Adams
2010-12-08 1:51 ` Juri Linkov
2010-12-08 3:03 ` Drew Adams
2010-12-06 23:03 ` Juri Linkov
2010-12-06 23:46 ` Lennart Borgman
2010-12-08 1:44 ` Juri Linkov
2010-12-07 3:48 ` Stefan Monnier
2010-12-08 1:57 ` Juri Linkov
2010-12-08 2:19 ` Lennart Borgman
2010-12-09 1:25 ` Juri Linkov
2010-12-08 3:10 ` Drew Adams
2010-12-09 14:31 ` Stefan Monnier
2010-12-09 16:14 ` Drew Adams
2010-12-10 3:09 ` Stefan Monnier
2010-12-09 14:28 ` Stefan Monnier
2010-12-09 17:43 ` Drew Adams
2010-12-10 3:06 ` Stefan Monnier
2010-12-10 3:46 ` Drew Adams
2010-12-10 20:10 ` Stefan Monnier
2010-12-08 3:32 ` Lennart Borgman
2012-09-20 8:30 ` bug#7567: Please add a history argument " Juri Linkov
2012-09-20 21:59 ` Juri Linkov
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=DF06262AA19C4341B1B745D93DC6ABA0@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7567@debbugs.gnu.org \
--cc=lennart.borgman@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.
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.