unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, Martin Fischer <parozusa@web.de>
Subject: Re: 22.1.90; desktop-save throws (error "No buffer named <uniquified buffername>")
Date: Tue, 12 Feb 2008 05:15:10 +0100	[thread overview]
Message-ID: <f7ccd24b0802112015w1bdd27alf800b41e97262d3c@mail.gmail.com> (raw)
In-Reply-To: <jwvhcgex2w7.fsf-monnier+emacs@gnu.org>

On Feb 12, 2008 4:39 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> Yes, very much so.

Glad to hear.

> > +(defun uniquify-buffer-base-name ()
> > +  "Return the base name of the current buffer."
> > +  (and (bound-and-true-p uniquify-managed)
> > +       (uniquify-item-base (car uniquify-managed))))
>
> There's a (defvar uniquify-managed nil ...) earlier in that file, so you
> shouldn't need the `bound-and-true-p', just use

Hmm.  IIUC, you're saying than if `uniquify-buffer-base-name' is run,
then uniquify.el has been loaded and so `uniquify-managed' will be
bound, even if it has no buffer-local value for the buffer being
tested... You're right. I was thinking of cases when uniquify.el were
not loaded, but they don't apply here.

>    (defun uniquify-buffer-base-name ()
>      "Return the base name of the current buffer.
>    Return nil if the buffer is not managed by uniquify."

OK.

             Juanma




  reply	other threads:[~2008-02-12  4:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 16:12 22.1.90; desktop-save throws (error "No buffer named <uniquified buffername>") Martin Fischer
2008-02-07  0:23 ` Juanma Barranquero
2008-02-08 16:59 ` Juanma Barranquero
2008-02-08 18:30   ` Stefan Monnier
2008-02-08 19:00     ` Juanma Barranquero
2008-02-08 21:17       ` Stefan Monnier
2008-02-12  0:44         ` Juanma Barranquero
2008-02-12  3:39           ` Stefan Monnier
2008-02-12  4:15             ` Juanma Barranquero [this message]
2008-02-27 12:43 ` Martin Fischer
2008-02-27 12:48   ` Juanma Barranquero
2008-02-27 16:28     ` Juanma Barranquero
2008-02-27 21:18       ` Stefan Monnier
2008-02-27 22:17         ` Juanma Barranquero
2008-02-27 22:37           ` Stefan Monnier
2008-02-27 23:00             ` Juanma Barranquero
2008-02-28  1:54               ` Stefan Monnier
2008-02-28  9:14                 ` Juanma Barranquero
2008-02-28 17:09                   ` Stefan Monnier
2008-02-28 13:27   ` Martin Fischer
2008-02-28 16:29     ` Juanma Barranquero
2008-02-29 10:07       ` Martin Fischer
2008-02-29 10:49         ` Juanma Barranquero
2008-02-29 13:17           ` Martin Fischer
2008-02-29 14:24             ` Juanma Barranquero
2008-02-29 14:48               ` Jason Rumney
2008-02-29 15:03                 ` Juanma Barranquero
2008-02-29 15:16                   ` Lennart Borgman (gmail)
2008-02-29 15:19                     ` Juanma Barranquero

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=f7ccd24b0802112015w1bdd27alf800b41e97262d3c@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=parozusa@web.de \
    /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).