From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Making buffer names unique
Date: Fri, 05 Sep 2008 21:37:16 -0600 [thread overview]
Message-ID: <g9stt6$64v$1@ger.gmane.org> (raw)
In-Reply-To: <BLU105-W59374FDC0E303E13E8D0B3DA580@phx.gbl>
Corey Foote wrote:
> I found the section in the Emacs manual on how to make buffer names
> unique (16.7.1), 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
> uniquify-buffer-name-style "forward") in my .emacs file, but it doesn't
> seem to do anything. Would anybody mind explaining to me how to user the
> forward naming method for my buffers? Thanks!
That variable's value should be a symbol, not a string:
(setq uniquify-buffer-name-style 'forward)
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2008-09-06 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 17:55 Making buffer names unique Corey Foote
2008-09-06 3:37 ` Kevin Rodgers [this message]
[not found] <mailman.18552.1220637357.18990.help-gnu-emacs@gnu.org>
2008-09-06 1:34 ` Will Parsons
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='g9stt6$64v$1@ger.gmane.org' \
--to=kevin.d.rodgers@gmail.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).