Re: *Occur in buf*?

[Sam Steingold <sds@gnu.org>]

> * In message <200207310554.g6V5swA16517@aztec.santafe.edu>
> * On the subject of "Re: *Occur in buf*?"
> * Sent on Tue, 30 Jul 2002 23:54:58 -0600 (MDT)
> * Honorable Richard Stallman <rms@gnu.org> writes:
>
>     > I know, but the idea was to rename the occur buffer automatically to
>     > include the name of the original buffer.  E.g. *Occur: xdisp.c* .
> 
>     TRT, IMO, is to make `generate-new-buffer-name' mode-specific.
>     E.g., have a buffer-local variable 'uniquify-buffer-name' or a similar
>     property of the major-mode name, which would hold a mode-specific
>     function which is to be run in the buffer being renamed.
> 
> This could be a reasonable idea.  Do people agree that there
> is a particular "right" behavior for any given mode?

there is probably "right" behavior for most "*foo*" modes.
for file-visiting buffers &c we can always resort to <n>.

-- 
Sam Steingold (http://www.podval.org/~sds) running RedHat7.3 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
Whether pronounced "leenooks" or "line-uks", it's better than Windows.