From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: uniquify-buffer-name-style
Date: Sun, 28 May 2006 22:01:23 -0500 (CDT) [thread overview]
Message-ID: <200605290301.k4T31Nqd004384@jane.dms.auburn.edu> (raw)
Setting `uniquify-buffer-name-style' outside Custom currently only
takes effect after uniquify.el is loaded. This misfeature is caused
by the use of defadvice in uniquify.el. As getting rid of this advice
in uniquify.el requires non-trivial changes to the C code, I do not
believe that it would be advisable to do this at the present time.
In the patch below, I just document the misfeature and add a comment
about the desirability to get rid of it instead. I can install if
desired.
===File ~/uniquify.el-diff==================================
*** uniquify.el 06 Feb 2006 16:02:02 -0600 1.61
--- uniquify.el 28 May 2006 21:09:47 -0500
***************
*** 93,99 ****
"Unique buffer names dependent on file name."
:group 'applications)
!
(defcustom uniquify-buffer-name-style nil
"*If non-nil, buffer names are uniquified with parts of directory name.
The value determines the buffer name style and is one of `forward',
--- 93,100 ----
"Unique buffer names dependent on file name."
:group 'applications)
! ;; The last paragraph of the docstring below should really be made obsolete
! ;; by eliminating the dependence on advice.
(defcustom uniquify-buffer-name-style nil
"*If non-nil, buffer names are uniquified with parts of directory name.
The value determines the buffer name style and is one of `forward',
***************
*** 104,110 ****
reverse name\\mumble\\bar name\\mumble\\quux
post-forward name|bar/mumble name|quux/mumble
post-forward-angle-brackets name<bar/mumble> name<quux/mumble>
! nil name name<2>"
:type '(radio (const forward)
(const reverse)
(const post-forward)
--- 105,116 ----
reverse name\\mumble\\bar name\\mumble\\quux
post-forward name|bar/mumble name|quux/mumble
post-forward-angle-brackets name<bar/mumble> name<quux/mumble>
! nil name name<2>
!
! This variable only takes effect when uniquify.el is loaded. If you set
! this variable in your .emacs, also specify `(require 'uniquify)'.
! Setting this variable through Custom automatically loads uniquify.el if it
! is not already loaded."
:type '(radio (const forward)
(const reverse)
(const post-forward)
============================================================
next reply other threads:[~2006-05-29 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 3:01 Luc Teirlinck [this message]
2006-05-29 21:28 ` uniquify-buffer-name-style Richard Stallman
2006-05-29 21:39 ` uniquify-buffer-name-style Luc Teirlinck
2006-05-30 16:00 ` uniquify-buffer-name-style Richard Stallman
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=200605290301.k4T31Nqd004384@jane.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).