From: Miles Bader <snogglethorpe@gmail.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: GDB startup
Date: Wed, 16 Feb 2005 12:06:18 +0900 [thread overview]
Message-ID: <fc339e4a05021519065125ef8f@mail.gmail.com> (raw)
In-Reply-To: <jwvfyzxnwus.fsf-monnier+emacs@gnu.org>
On Tue, 15 Feb 2005 20:16:02 -0500, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> I guess post-command-hook is the closest thing.
It gets used way too much though -- we shouldn't be sticking all kinds
of random crap on post-command-hook...
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-02-16 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 15:53 GDB startup Stefan Monnier
2005-02-15 21:35 ` Nick Roberts
2005-02-16 1:16 ` Stefan Monnier
2005-02-16 2:44 ` Nick Roberts
2005-02-16 3:06 ` Miles Bader [this message]
2005-02-16 14:07 ` Kim F. Storm
2005-02-16 14:39 ` Luc Teirlinck
2005-02-16 14:47 ` 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=fc339e4a05021519065125ef8f@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=nickrob@snap.net.nz \
/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).