unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Subject: Uniquify
Date: Fri, 09 May 2003 09:36:07 -0400	[thread overview]
Message-ID: <200305091336.h49Da7wP024061@rum.cs.yale.edu> (raw)


OK, I think i'm finally done with my uniquify hacking and there's
two things still left for me to do:

- Revert the patch that made Gnus' "(un)sent" buffers unmanaged.  The new
  code should handle those buffers correctly: either they'll be unmanaged
  anyway (if Gnus never calls either `create-file-buffer' on them or
  `rename-buffer' with a non-nil `unique' argument) or they'll be managed
  but uniquify will still preserve their name.  I.e. if the buffer-file-name
  is ~/foo/drafts/7 and the buffer-name was "*unsent bar*", uniquify
  will at worst use a buffer-name of the form "*unsent bar*|foo/drafts"

- Change the default of uniquify-after-kill-buffer-p to t (we could
  also change its name, but I don't care enough to do it myself).
  The docstring of uniquify-after-kill-buffer-p used to say that it's
  a dangerous feature because it can change buffer names behind packages'
  backs and that if packages remember their buffers by name (rather
  than directly by buffer) there can be trouble.
  I removed that text because the text applies to the whole of uniquify
  rather than just to uniquify-after-kill-buffer-p.  OTOH, it is true
  that uniquify-after-kill-buffer-p made the problem slightly worse because
  it caused all buffer-names to be reconsidered after a kill-buffer,
  including buffers which had never been uniquified before.  This has
  now been fixed, so I think we can safely change the default.


	Stefan


--- uniquify.el.~1.49.~	Fri May  9 09:17:05 2003
+++ uniquify.el	Fri May  9 09:19:34 2003
@@ -111,7 +111,7 @@
 		(const :tag "standard Emacs behavior (nil)" nil))
   :require 'uniquify)
 
-(defcustom uniquify-after-kill-buffer-p nil
+(defcustom uniquify-after-kill-buffer-p t
   "If non-nil, rerationalize buffer names after a buffer has been killed."
   :type 'boolean)
 
@@ -122,7 +122,7 @@
   :type 'boolean)
 
 ;; The default value matches certain Gnus buffers.
-(defcustom uniquify-ignore-buffers-re "^\\*\\(un\\)?sent "
+(defcustom uniquify-ignore-buffers-re nil
   "*Regular expression matching buffer names that should not be uniquified.
 For instance, set this to \"^draft-[0-9]+$\" to avoid having uniquify rename
 draft buffers even if `uniquify-after-kill-buffer-p' is non-nil and the

                 reply	other threads:[~2003-05-09 13:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200305091336.h49Da7wP024061@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.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).