From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: break signal on Mac OS X doesn't work
Date: Fri, 24 Dec 2004 11:53:42 -0500 [thread overview]
Message-ID: <barmar-A82F1C.11534224122004@comcast.dca.giganews.com> (raw)
In-Reply-To: mailman.8535.1103860328.27204.help-gnu-emacs@gnu.org
In article <mailman.8535.1103860328.27204.help-gnu-emacs@gnu.org>,
David Goodger <goodger@python.org> wrote:
> System identification: I'm running GNU Emacs 21.3.50.1 on Mac OS X
> 10.3.7. It runs in a window that starts out saying "Terminal" in the
> title bar, before Emacs takes over. My .emacs file contains this
> setup code:
>
> ; shell mode
> (setq explicit-shell-file-name "bash")
> (setq explicit-bash-args '("--login" "--noediting" "-i"))
> (add-hook 'shell-mode-hook 'my-shell-mode-hook)
> (defun my-shell-mode-hook ()
> "Customize shell-mode"
> (define-key shell-mode-map "\C-cf" 'font-lock-mode)
> (define-key shell-mode-map '[C-return] 'shell-enter-and-resync-dirs)
> (setq tab-width 8)
> (setq font-lock-mode nil))
>
> The problem is when I open a shell ("M-x shell"), I can't stop a
> process with a BREAK signal (typing C-c C-c or choosing BREAK from the
> Signals menu). I see "C-c C-c" in the shell window, but the process
> doesn't halt.
>
> Any clues to what's going on here? Thanks in advance.
I've seen the same thing, but only when the command I'm trying to
interrupt is setuid. I posted here (or maybe in a comp.sys.mac group)
months ago and never got a useful answer.
The workaround is to type "C-q C-c RET" to send a literal Control-C
rather than a signal.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next parent reply other threads:[~2004-12-24 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8535.1103860328.27204.help-gnu-emacs@gnu.org>
2004-12-24 16:53 ` Barry Margolin [this message]
2004-12-24 23:03 ` break signal on Mac OS X doesn't work David Goodger
2004-12-25 0:31 ` David Goodger
2004-12-24 3:31 David Goodger
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=barmar-A82F1C.11534224122004@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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.
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).