[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7567: Please add a history variable to read-regexp
From: |
Lennart Borgman |
Subject: |
bug#7567: Please add a history variable to read-regexp |
Date: |
Wed, 8 Dec 2010 03:19:47 +0100 |
On Wed, Dec 8, 2010 at 2:57 AM, Juri Linkov <juri@jurta.org> wrote:
>> So after reading the rest of the thread, I think I finally understand
>> that you want to "add a history *argument* to read-regexp", right?
>> Then it sounds perfectly acceptable.
>
> For consistency, `read-regexp' could have the same function signature
> as other minibuffer reading functions, e.g. like `read-string':
>
> (read-string PROMPT &optional INITIAL-INPUT HISTORY DEFAULT-VALUE
> INHERIT-INPUT-METHOD)
>
> (read-regexp PROMPT &optional INITIAL-INPUT HISTORY DEFAULT-VALUE
> INHERIT-INPUT-METHOD)
I agree.
In addition to that when we have that in place then a number of places
in the code should be updated to use it instead of read-string. (And
some new history vars for it should be added.)
bug#7567: Please add a history variable to read-regexp, Juri Linkov, 2010/12/06
bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 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, Stefan Monnier, 2010/12/09
- bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/09
- bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 2010/12/09
bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 2010/12/09
bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/09
bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 2010/12/09
bug#7567: Please add a history variable to read-regexp, Drew Adams, 2010/12/09
bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 2010/12/10