when emacs gets interrupted

when emacs gets interrupted

[Dan Jacobson]

Can you please do something about when ones does
$ emacs #which starts emacs in another window
C-c #which kills emacs

Why can't you ask there in the shell 'are you serious?'

As an example of the crap effects,
$ emacs file #and in that file type 3 short lines, then back in the shell:
C-c

Where did your three lines go?  not even a #file# backup!
Why can't you at least auto-save when you get such a signal?
Isn't that a wonderful time for an auto-save? Sure,
$ emacs&disown
is what we are supposed to do perhaps, but still, where's that safety
net?  I didn't do kill -9 you know.

The problem occurs mostly when the user gets his background jobs
confused, but that's besides the point.
-- 
http://jidanni.org/ Taiwan(04)25854780

Re: when emacs gets interrupted

[Kevin Rodgers]

Dan Jacobson wrote:

> Can you please do something about when ones does
> $ emacs #which starts emacs in another window
> C-c #which kills emacs
> 
> Why can't you ask there in the shell 'are you serious?'


Because that is the behavior I expect.  When I send SIGINT to a process, I want

it to terminate.

Perhaps you should write your own script that traps SIGINT before calling Emacs,
and handles the signal the way you want.


> As an example of the crap effects,
> $ emacs file #and in that file type 3 short lines, then back in the shell:
> C-c
> 
> Where did your three lines go?  not even a #file# backup!
> Why can't you at least auto-save when you get such a signal?

 > Isn't that a wonderful time for an auto-save?

I suspect you did not reach the auto-save threshold.  Try decreasing
auto-save-interval.


-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>