Re: Poll on wildcard listings
Amir J. Katz (amir@ddddf.com)
Wed, 5 Jul 95 10:34:59 IDT
>>>>> "Sandy" == Sandy Rutherford <sandy@math.ubc.ca> writes:
Sandy> I'd like to get some feedback on how wildcard dired buffers should be
Sandy> named.
Sandy> For example if you have dired buffers for /foo/bar/ and for
Sandy> /foo/bar/a*, should the second buffer be named:
Sandy> (1) bar<2> (Standard Emacs convention for files)?
Standard but non-informative as hell :-)
Sandy> (2) bar<a*> (An attempt to be more informative than (1), but could
Sandy> lead to weird names like bar<b*><2>)?
Agreed
Sandy> (3) bar/a* (A bit nonstandard, as "/" isn't usually used in buffer
Sandy> names.)?
Oy-vey (as they say in Jewish)
Sandy> (4) Other ideas, suggestions, or comments?
If you ever used the 'uniquify.el' package, it names buffers with
identical basename by the full pathname going backward, separated
with vertical bars:
file buffer name
---------------------------------
a/b/c/foobar.c --> foobar.c|c|b|a
a/x/y/foobar.c --> foobar.c|y|x|a
This way the basename is always visible in the modeline even if the
rest of the buffer name gets truncated due to modeline limitations.
/* Amir J. Katz email: amir@ddddf.com */
/* Fourth Dimension Software, LTD., Tel-Aviv, ISRAEL */
/* ... Any closet is a walk-in closet if you try hard enough ... */
/* ... (Steven Wright) ... */