From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: GUD icons
Date: Wed, 16 Nov 2005 13:16:21 +1300 [thread overview]
Message-ID: <17274.31317.756735.907088@kahikatea.snap.net.nz> (raw)
In-Reply-To: <m3irutlden.fsf@kfs-l.imdomain.dk>
> However, I had only tried this with debugging emacs, so indeed C-c C-c kills
> emacs -- so I'm accustomed to ALWAYS use C-c C-z (stop), as this is safer.
>
> > SIGTSTP (comint-stop-subjob) needs two continue commands to restart
> > whereas SIGINT only needs one:
>
> Yes, that is annoying (but I'm so used to it, that I hardly think
> about it anymore).
You could put this in ~/.gdbinit:
handle SIGTSTP nopass
> > The only problem with using SIGINT is that it doesn't work when debugging
> > Emacs.
>
> Why not?
Its explained in DEBUG:
The src/.gdbinit file in the Emacs distribution arranges for SIGINT
(C-g in Emacs) to be passed to Emacs and not give control back to GDB.
Actually this only seems to be necessary when Emacs is running in a
terminal.
> > I could make this a special case, as with gud-pp, I guess.
>
> Wouldn't it be better to make emacs work with SIGINT instead?
In general, it can't, for the reason above.
> But if SIGINT can kill emacs, it can kill other apps too (I suppose);
> so for that reason SIGTSTP is safer -- but if emacs is really the only
> app where this is relevant, maybe we could special-case it.
It would generally only be the case if the the app has its own use for SIGINT.
Nick
next prev parent reply other threads:[~2005-11-16 0:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 22:15 [PATCH] left-fringe for speedbar Nick Roberts
2005-11-12 23:27 ` Drew Adams
2005-11-13 0:47 ` Nick Roberts
2005-11-13 2:44 ` Miles Bader
2005-11-13 2:57 ` Nick Roberts
2005-11-13 3:19 ` Miles Bader
2005-11-13 4:36 ` Nick Roberts
2005-11-13 6:06 ` Miles Bader
2005-11-14 4:54 ` Richard M. Stallman
2005-11-14 20:07 ` Nick Roberts
2005-11-14 23:08 ` Kim F. Storm
2005-11-15 2:09 ` Nick Roberts
2005-11-15 9:47 ` Kim F. Storm
2005-11-15 12:37 ` GUD icons [was: Re: [PATCH] left-fringe for speedbar] Nick Roberts
2005-11-15 15:25 ` Kim F. Storm
2005-11-15 22:49 ` GUD icons Nick Roberts
2005-11-15 23:06 ` Kim F. Storm
2005-11-16 0:16 ` Nick Roberts [this message]
2005-11-16 0:20 ` Andreas Schwab
2005-11-15 18:07 ` [PATCH] left-fringe for speedbar Richard M. Stallman
2005-11-15 23:00 ` Nick Roberts
2005-11-13 3:13 ` Drew Adams
2005-11-13 4:02 ` Nick Roberts
2005-11-13 2:53 ` Nick Roberts
2005-11-13 20:40 ` Kim F. Storm
2005-11-13 22:26 ` Nick Roberts
2005-11-14 0:20 ` Kim F. Storm
2005-11-14 1:26 ` Nick Roberts
2005-11-14 14:16 ` Kim F. Storm
2005-11-14 19:57 ` Nick Roberts
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=17274.31317.756735.907088@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--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).