From: Will Parsons <oudeis@nodomain.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Making buffer names unique
Date: 6 Sep 2008 01:34:15 GMT [thread overview]
Message-ID: <slrngc3ngn.r5p.oudeis@isis.thalatta.eme> (raw)
In-Reply-To: mailman.18552.1220637357.18990.help-gnu-emacs@gnu.org
Corey Foote wrote:
> I found the section in the Emacs manual on how to make
> buffer names unique (16.7.1)=2C but am having trouble actually getting that=
> to work for
> me. I'm sure it must be something I'm doing wrong. I tried putting (setq un=
> iquify-buffer-name-style "forward") in my .emacs file=2C but it doesn't see=
> m to do anything. Would anybody mind
> explaining to me how to user the forward naming method for my buffers? Than=
> ks!
I have in my .emacs file:
(require 'uniquify)
(setq uniquify-buffer-name-style 'post-forward)
--
Will
next parent reply other threads:[~2008-09-06 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18552.1220637357.18990.help-gnu-emacs@gnu.org>
2008-09-06 1:34 ` Will Parsons [this message]
2008-09-05 17:55 Making buffer names unique Corey Foote
2008-09-06 3:37 ` Kevin Rodgers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrngc3ngn.r5p.oudeis@isis.thalatta.eme \
--to=oudeis@nodomain.invalid \
--cc=ellenophilos@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).