[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: |
Richard M Stallman |
Subject: |
bug#1800: 23.0.60; Changed meaning of * in buffer name completion |
Date: |
Tue, 06 Jan 2009 17:59:44 -0500 |
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]
That is a good idea. It would provide the same benefit of the
existing feature, but without the inconvenience.
- bug#1800: 23.0.60; Changed meaning of * in buffer name completion, (continued)
- 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
- 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, Juri Linkov, 2009/01/07
bug#1800: 23.0.60; Changed meaning of * in buffer name completion,
Richard M Stallman <=