Re: args for uniquify-rationalize-file-buffer-names

[Roland Winkler]

On Mon Dec 27 2004 Stefan Monnier wrote:
> >> The function uniquify-rationalize-file-buffer-names has three
> >> mandatory arguments but the call of interactive doesn't specify any
> >> of them.
> 
> I don't have time to look at it right now, but I'll keep it in my TODO list.
> 
> >> I think it's a mistake for this function to be interactively callable,
> >> and that clearly didn't work, so I'll delete the interactive spec.
> > Previous versions of emacs had this interactive function in order to
> > re-uniquify buffer names when the uniquified buffer names are
> > screwed up (e.g., when files are renamed using dired, then the
> > corresponding uniquified buffer names are not (not always?)
> > updated). It would be nice if there was still such an interactive
> > function to ensure that uniquified buffer names are up to date.
> 
> I can't remember seeing a bug-report about this.
> Could you send one (ideally easy to reproduce, of course).

Say the value of uniquify-buffer-name-style is 'forward. Then two
buffers visiting the files ~/a/foo and ~/b/foo have the names a/foo
and b/foo. When we rename directory ~/b to ~/c using dired, the name
of the buffer visiting the file ~/c/foo remains b/foo which is
incorrect. Buffer names are also screwed up, e.g., when write buffer
b/foo into file ~/c/foo. Again the buffer name remains b/foo. I
guess there are many other possibilities to screw up uniquified
buffer names.

With previous versions of emacs, it was possible to re-uniquify the
buffer names using uniquify-rationalize-file-buffer-names. This
function was the interactive entry point of uniquify. I think that
such a command is very important because it would be very difficult
to have a foolproof fully automatic algorithm giving always
up-to-date uniquified buffer names. Possibly one could give this
command a shorter, "more mnemonic" name.

Roland