bug#7567: Please add a history variable to read-regexp

[Lennart Borgman <lennart.borgman@gmail.com>]

On Mon, Dec 6, 2010 at 11:57 PM, Drew Adams <drew.adams@oracle.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.
>
> 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?


Thanks for asking, I thought it was clear.

Why should that regexp be used to make buffer names? It is probably a
regexp that has been used for matching strings in buffers. (It might
of course be a regexp from a search in *Buffer List*, but that is not
the normal case.)