help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to avoid having shell scripts which fail from killing Emacs shel


From: David Karr
Subject: Re: How to avoid having shell scripts which fail from killing Emacs shell?
Date: Mon, 22 Jun 2009 16:08:35 -0700 (PDT)
User-agent: G2/1.0

On Jun 22, 3:49 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 22.06.2009 um 22:21 schrieb David Karr:
>
> > I note that even though the Java class throws an exception, it doesn't
> > cause the script to exit at that point. I tried putting an "echo"
> > right after the Java call, and it executes fine.  Right after that (as
> > it's the last line in the script), the script exits, and at my shell
> > prompt, I see "% exit" (where "%" is my PS1), and my shell buffer
> > terminates.
>
> Could you try it with other shells, too? You still have no proof that  
> your bash is *not* broken. And, for another series of tests, you  
> could try the same in another account. And particularly when  
> launching GNU Emacs without customisation ...
>
> Besides this, the bash in *shell* buffer can be initialised  
> differently than in an xterm. Bash is complicated.
>
> OK, I do remember similiar events! It was in tcsh. And there were two  
> or three problems: a script was running wild, I was typing C-c or  
> such wildly, and ... well, it could have been in cpan (filling up my  
> root and boot file system). Anyway, in the end I saw the shell die,  
> and at this moment it's not possible to gain more information. There  
> were also events outside cpan. I do remember that I made mistakes,  
> typing C-d for example. There could be one plausible cause: when you  
> type input and your script is not prepared to read this, then GNU  
> Emacs has to save it. Maybe this period is limited. And then  
> something irregular could happen. I have no real idea, but what you  
> encounter is not impossible. (And maybe Cygwin adds something to make  
> it happen, it's an emulation in a host operating system.)
>
> There is no chance to make the tests in a real UNIX environment?

My current test case has the Java class taking a line of input from
stdin.  I guess I'll build an experimental class that takes the file
name from the command line parameter instead of stdin, and test that
on both Cygwin and Linux.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]