* break signal on Mac OS X doesn't work
@ 2004-12-24 3:31 David Goodger
0 siblings, 0 replies; 4+ messages in thread
From: David Goodger @ 2004-12-24 3:31 UTC (permalink / raw)
[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]
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.
--
David Goodger <http://python.net/~goodger>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: break signal on Mac OS X doesn't work
[not found] <mailman.8535.1103860328.27204.help-gnu-emacs@gnu.org>
@ 2004-12-24 16:53 ` Barry Margolin
2004-12-24 23:03 ` David Goodger
0 siblings, 1 reply; 4+ messages in thread
From: Barry Margolin @ 2004-12-24 16:53 UTC (permalink / raw)
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 ***
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: break signal on Mac OS X doesn't work
2004-12-24 16:53 ` break signal on Mac OS X doesn't work Barry Margolin
@ 2004-12-24 23:03 ` David Goodger
2004-12-25 0:31 ` David Goodger
0 siblings, 1 reply; 4+ messages in thread
From: David Goodger @ 2004-12-24 23:03 UTC (permalink / raw)
[-- Attachment #1.1: Type: text/plain, Size: 609 bytes --]
[Barry Margolin]
> I've seen the same thing, but only when the command I'm trying to
> interrupt is setuid.
Mine aren't setuid. It's any command at all -- I can't interrupt
anything. For example,
while [ 1 ] ; do sleep 1 ; done
I end up having to open up another shell, and kill the process
from there.
> 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.
Even that doesn't work for me :-(
Thanks for replying!
--
David Goodger <http://python.net/~goodger>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: break signal on Mac OS X doesn't work
2004-12-24 23:03 ` David Goodger
@ 2004-12-25 0:31 ` David Goodger
0 siblings, 0 replies; 4+ messages in thread
From: David Goodger @ 2004-12-25 0:31 UTC (permalink / raw)
[-- Attachment #1.1: Type: text/plain, Size: 349 bytes --]
[Barry Margolin]
>> The workaround is to type "C-q C-c RET" to send a literal Control-C
>> rather than a signal.
[David Goodger]
> Even that doesn't work for me :-(
But Barry's off-list suggestion to examine process-connection-type
led to a solution:
(setq process-connection-type t)
Thanks Barry!
--
David Goodger <http://python.net/~goodger>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
Help-gnu-emacs mailing list
Help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-12-25 0:31 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.8535.1103860328.27204.help-gnu-emacs@gnu.org>
2004-12-24 16:53 ` break signal on Mac OS X doesn't work Barry Margolin
2004-12-24 23:03 ` David Goodger
2004-12-25 0:31 ` David Goodger
2004-12-24 3:31 David Goodger
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).