From: Lennart Borgman <lennart.borgman@gmail.com>
To: 7567@debbugs.gnu.org
Subject: bug#7567: Please add a history variable to read-regexp
Date: Mon, 6 Dec 2010 23:43:04 +0100 [thread overview]
Message-ID: <AANLkTik3u8vJCbsk=w+Lrbcyn5m97fY2JieAYwfPAnse@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik-PEdh+Z7SQ--ipdOrLJvuHfcmUihvXoWnqope@mail.gmail.com>
On Mon, Dec 6, 2010 at 3:24 AM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> Also take care of the strange query-replace-from-history-variable in
> read-regexp.
No answer. Was something unclear here?
The current read-regexp use is problematic for example in
multi-isearch-read-matching-buffers and
multi-occur-in-matching-buffers. I think a common history variable
could be used for those cases, but they currently use the default
regexp-history variable which seems totally inappropriate.
next prev parent reply other threads:[~2010-12-06 22:43 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 [this message]
2010-12-06 22:57 ` Drew Adams
2010-12-06 23:00 ` Lennart Borgman
2010-12-06 23:11 ` Drew Adams
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='AANLkTik3u8vJCbsk=w+Lrbcyn5m97fY2JieAYwfPAnse@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=7567@debbugs.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.