[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#1800: 23.0.60; Changed meaning of * in buffer name completion
From: |
Juri Linkov |
Subject: |
bug#1800: 23.0.60; Changed meaning of * in buffer name completion |
Date: |
Tue, 06 Jan 2009 21:00:34 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (x86_64-pc-linux-gnu) |
> The change to treat * as a wildcard is often a pain in the neck.
> Such changes should not be made without polling the users first.
>
> Please undo this change, poll the users, and redo the change
> if they generally want it.
This is a nice feature, but I have the same problems with it.
Trying to switch to a killed buffer that had `*' at the beginning
of its name (e.g. *grep*) typing `* g TAB' displays a large list
of irrelevant buffer names.
Regular expressions allow a backslash before `*' for a literal character.
So `\ * g TAB' could try completion literally without interpreting
`*' as a wildcard. But I think this would be inconvenient.
A better variant is to provide two-step completion. So when there is
no buffer matching `*g' literally then display a message like
[No match, type TAB again for * as a wildcard]
--
Juri Linkov
http://www.jurta.org/emacs/
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Richard M Stallman, 2009/01/06
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion,
Juri Linkov <=
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Drew Adams, 2009/01/06
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Juri Linkov, 2009/01/06
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Drew Adams, 2009/01/07
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Juri Linkov, 2009/01/07
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Drew Adams, 2009/01/07
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, Drew Adams, 2009/01/07