Re: Info - uniquify incompatibility ...

From: Volker Franz <volker.franz(a)tuebingen.mpg.de&gt; Date: Wed, 10 Oct 2001 20:53:37 +0200 I am glad you like the suggestion! n> This is still not ideal, because the real criterion is n> `buffers whose mode is Info-mode'; this will still break n> people who rename their Info buffers themselves. One more idea (for generality): One could restrict uniquify to change only buffers for which the basename corresponds to the visited file. Example: buffer-base-name file-name change-allowed ----------------------------------------------------------- *info* new-users-guide.info-1 no *info* dir no foo ~/bar1/foo yes foo ~/bar2/foo yes I think this would solve the problem without having to explicitly specify which modes (or files) should be excluded... But I do not know how much coding effort this would be (and unfortunately will have no time to check during the next weeks :-( A slightly different idea is to integrate things like info, hyper apropos, mail, etc with uniquify. Eg, if I am using uniquify then different packages like info/hyper apropos/mail should create uniquified names - eg info<vm>, reply<xemacs-beta>, apropos<uniquify> I can never remember the naming scheme for the different buffers like info and apropos - does it start with a space, a *? was that H or h? -jeff