[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: |
Thu, 9 Dec 2010 19:46:23 -0800 |
> >> No: new such functions should not offer both INITIAL-INPUT and
> >> DEFAULT-VALUE. Instead, they should (like read-regexp) only accept
> >> DEFAULT-VALUE (and automatically add it to the prompt in
> >> the standard format).
>
> > Let INITIAL-INPUT be. -- John Lennon
>
> > No one is forced to use it. What did it ever do to you? ;-)
>
> It's too low-level: better provide a DEFAULT-VALUE and then
> the function
What function?
> can decide to do as we do (i.e. put default in prompt and in
> M-n) or as they do
They who/what?
> (put it as the initial contents, selected so that
> delete-selection-mode can get rid of it in a pinch).
Who/what does that, and how?
- bug#7567: Please add a history variable to read-regexp, (continued)
- 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 <=
- bug#7567: Please add a history variable to read-regexp, Stefan Monnier, 2010/12/10
bug#7567: Please add a history variable to read-regexp, Lennart Borgman, 2010/12/07