[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: uniquify
From: |
Dennis Yurichev |
Subject: |
Re: uniquify |
Date: |
Sun, 22 Jun 2014 01:01:47 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) |
Alex Kost <alezost@gmail.com> writes:
>> I added this to my .emacs:
>> ===================================================
>> (require 'uniquify)
>> (setq uniquify-buffer-name-style 'forward)
>> ===================================================
>> But nothing happens, buffer names still has <n> at the end.
>>
>> What/where should I check?
>> I've got GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601).
>
> If you mean the buffers like "*shell*<2>" or "*info*<2>" then it should
> be so. "uniquify" deals only with the buffers that have the same name.
> For example if you open 2 files "temp.el" from different directories,
> than "uniquify" will uniquify them.
I found a problem.
Maybe that story will be useful for someone, so I'll post it here.
My Emacs saving buffer configuration into emacs.desktop file
automatically, so names like main.tex<2> and main.tex<3> were saved and
reloaded there each time at startup, and uniquify.el hasn't any chance to
name them properly.
My bad!
--
-- http://yurichev.com
- uniquify, Dennis Yurichev, 2014/06/20
- Message not available
- Message not available
- Re: uniquify,
Dennis Yurichev <=
- Prev by Date:
Re: uniquify
- Next by Date:
Swedish midsummer legends: IPC, collaborative Emacs, sed, awk, DWIM, Unix, and more
- Previous by thread:
Re: uniquify
- Next by thread:
Swedish midsummer legends: IPC, collaborative Emacs, sed, awk, DWIM, Unix, and more
- Index(es):