unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] find-file-noselect-1
Date: Sun, 13 Feb 2005 11:14:58 -0500	[thread overview]
Message-ID: <87mzu84eyh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <420EE62F.5020400@snap.net.nz> (Nick Roberts's message of "Sun, 13 Feb 2005 18:31:27 +1300")

> I am just using find-file-noselect to recover the name of the buffer.
> I have a buffer and a file associated with it.  Generally, I don't see the
> big deal whether I pass the buffer-name or filename across the functions.

When you know that the file necessarily corresponds to a buffer and you want
to do something to the buffer rather than to the file, then you really
should pass the buffer, not the file name.

> However since the code is part of find-file-hook, I'll pass the
> buffer-name to avoid the possibility of some kind of recursion.

Better pass the *buffer* rather than the *buffer name*.


        Stefan

  reply	other threads:[~2005-02-13 16:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 20:36 [PATCH] find-file-noselect-1 Nick Roberts
2005-02-11  0:19 ` Miles Bader
2005-02-11  2:49   ` Nick Roberts
2005-02-11  3:03     ` Nick Roberts
2005-02-12  8:38       ` Richard Stallman
2005-02-12 10:30         ` Nick Roberts
2005-02-12 16:50           ` Stefan Monnier
2005-02-13  5:31             ` Nick Roberts
2005-02-13 16:14               ` Stefan Monnier [this message]
2005-02-13 12:38           ` Richard Stallman
2005-02-13 20:49             ` Nick Roberts
2005-02-15  6:15               ` Richard Stallman
2005-02-11  3:16     ` Stefan Monnier
2005-02-11  3:19 ` Stefan Monnier
2005-02-11  8:08   ` Nick Roberts
2005-02-11  8:51     ` Kim F. Storm
2005-02-11  9:53       ` Nick Roberts
2005-02-11 10:30         ` Kim F. Storm
2005-02-11 10:05       ` Miles Bader
2005-02-11 10:29         ` Kim F. Storm
2005-02-11 10:44           ` Nick Roberts
2005-02-11 13:05             ` Kim F. Storm

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=87mzu84eyh.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.
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).