[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7567: Please add a history variable to read-regexp
From: |
Drew Adams |
Subject: |
bug#7567: Please add a history variable to read-regexp |
Date: |
Mon, 6 Dec 2010 14:57:40 -0800 |
> > 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.
I don't mean to meddle here, but it's not clear to me why `regexp-history' is
not appropriate in the contexts you mention. The user is inputting a regexp.
Why shouldn't previous regexps the user inputted be available in the input
history for this operation?
- bug#7567: Please add a history variable to read-regexp, Lennart Borgman, 2010/12/05
- bug#7567: Please add a history variable to read-regexp, Lennart Borgman, 2010/12/06
- bug#7567: Please add a history variable to read-regexp,
Drew Adams <=
- bug#7567: Please add a history variable to read-regexp, Lennart Borgman, 2010/12/06
- bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/06
- bug#7567: Please add a history variable to read-regexp, Lennart Borgman, 2010/12/06
- bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/06
- bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/06
- bug#7567: Please add a history variable to read-regexp, Juri Linkov, 2010/12/07
- bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/07
bug#7567: Please add a history variable to read-regexp, Juri Linkov, 2010/12/06