From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] find-file-noselect-1
Date: Sun, 13 Feb 2005 07:38:37 -0500 [thread overview]
Message-ID: <E1D0J1J-0008Im-A3@fencepost.gnu.org> (raw)
In-Reply-To: <16909.56012.478599.348349@farnswood.snap.net.nz> (message from Nick Roberts on Sat, 12 Feb 2005 23:30:36 +1300)
Is this what you mean?
More or less.
I don't think that gud-comint-buffer should be set to
nil because that would prevent the GDB session from recovering.
Perhaps you should add a new variable, which you can set if you catch
an error, to disable this hook from really doing anything once it has
had an error.
> Why call find-file-noselect there? If this is meant to operate on the
> file that was just visited, it already has a buffer, and it is the
> current buffer when gdb-find-file-hook runs. Why not just use
> that buffer?
That might have been true but I'm now using this function to address Kim's
point about enabling gud-minor-mode for existing buffers.
It sounds like you are in all cases trying to find an existing buffer.
So instead of using find-file-noselect, you could use
find-buffer-visiting.
next prev parent reply other threads:[~2005-02-13 12:38 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
2005-02-13 12:38 ` Richard Stallman [this message]
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=E1D0J1J-0008Im-A3@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).