[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10148: 24.0.91; "pending" regexp Isearch
From: |
Drew Adams |
Subject: |
bug#10148: 24.0.91; "pending" regexp Isearch |
Date: |
Wed, 30 Nov 2011 06:47:18 -0800 |
> Another option is to not say anything at all. I don't have a strong
> opinion on this, but I never found "pending" useful and I don't think
> I'd have felt differently if it had said "adjusted" instead.
+1
Or use some text that says what it means? You say it moves to another search
hit ("adjusts its position to another match").
Is that other search hit always the next/previous one (depending on direction)?
Or is it at least some simple, consistent movement that is easy to name?
If so, maybe just say that you are moving to the "[next]" match or some such.
Dunno - it's not clear to me what is involved. But it's also not clear to me
from either "pending" or "adjusted". And if you say nothing at all but move to
another search hit, that too might be confusing. HTH.
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/27
- bug#10148: 24.0.91; "pending" regexp Isearch, Juri Linkov, 2011/11/28
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/29
- bug#10148: 24.0.91; "pending" regexp Isearch, Juri Linkov, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Juri Linkov, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Stefan Monnier, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Dani Moncayo, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch,
Drew Adams <=
- bug#10148: 24.0.91; "pending" regexp Isearch, Juri Linkov, 2011/11/30
- bug#10148: 24.0.91; "pending" regexp Isearch, Stefan Monnier, 2011/11/30