From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sunil Yeddu Newsgroups: gmane.emacs.help Subject: Re: M-x shell not working Date: Tue, 18 Oct 2005 04:56:32 -0700 Message-ID: <13ecef2d0510180456p67bb4175ld3fa440af1f5390f@mail.gmail.com> References: <13ecef2d0510172334jd0c4e65i7cec30e4fd522811@mail.gmail.com> <708ac6dccd5c5bcbc601b8ebb3760da0@Web.DE> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1056609489==" X-Trace: sea.gmane.org 1129638951 2050 80.91.229.2 (18 Oct 2005 12:35:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 Oct 2005 12:35:51 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Oct 18 14:35:50 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ERqg6-0007rP-O1 for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Oct 2005 14:34:51 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ERqg6-0005uR-2b for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Oct 2005 08:34:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ERq55-00043Z-3e for help-gnu-emacs@gnu.org; Tue, 18 Oct 2005 07:56:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ERq53-00042s-Js for help-gnu-emacs@gnu.org; Tue, 18 Oct 2005 07:56:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ERq52-00042l-SI for help-gnu-emacs@gnu.org; Tue, 18 Oct 2005 07:56:33 -0400 Original-Received: from [64.233.184.207] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ERq53-0006cC-1P for help-gnu-emacs@gnu.org; Tue, 18 Oct 2005 07:56:33 -0400 Original-Received: by wproxy.gmail.com with SMTP id i11so24668wra for ; Tue, 18 Oct 2005 04:56:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=I+YhpHuZnBLsVzg0H2K0VVN+w3tD5+zhXKlHBf7Y7GyV1aSAb/r+l2aeH0jmKkK8jMtvZCcf+04n8u+96EVMtIdXEcM+89s4sfV3Gp9EgenuDLyqASXRvw2D4JL3l16cHdqdkM5RcuDjdIiHzRhjS2gze8+Ufi2sn9AVi3t4jZ0= Original-Received: by 10.54.138.7 with SMTP id l7mr95326wrd; Tue, 18 Oct 2005 04:56:32 -0700 (PDT) Original-Received: by 10.54.124.6 with HTTP; Tue, 18 Oct 2005 04:56:32 -0700 (PDT) Original-To: Peter Dyballa In-Reply-To: <708ac6dccd5c5bcbc601b8ebb3760da0@Web.DE> X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:30319 Archived-At: --===============1056609489== Content-Type: multipart/alternative; boundary="----=_Part_9402_11841642.1129636592173" ------=_Part_9402_11841642.1129636592173 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, There was a 'stty sane' line in my .cshrc which is causing the Invalid argument message. I removed it and that erorr message has gone away. Thanks= , Pete. I also noticed that setting TERM env to any value is causing shell to exit. I removed the line which sets TERM env from my cshrc and I was able to access shell !!! But the warning message is still there. Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. And setting TERM env in it is causing the shell to exit immediately. I gues= s this is because of tty not being allocated. From the shell in emacs when I type tty, I see... $ tty not a tty So there is no solution to the original problem yet, as removing the line which sets TERM env cannot be a permanent solution. Sunil On 10/18/05, Peter Dyballa wrote: > > > Am 18.10.2005 um 08:34 schrieb Sunil Yeddu: > > > Warning: no access to tty (Bad file descriptor). > > Thus no job control in this shell. > > stty: standard input: Invalid argument <<<<<<<<<<< > > exit > > > > Process shell finished > > This is very familiar for me on Mac OS X. Here it's found that using > ttys is not reliable. (setq process-connection-type t) in .emacs > 'corrects' this. > > Your problem is that some shell rc file writes something into /dev/tty > or such without first checking whether it's allowed or useful. So check > the code in your shell's rc file(s), for example make the shell > verbosely list what it's doing during its initialisation while working > on the rc file(s)! > > -- > Greetings > > Pete > > "One cannot live by television, video games, top ten CDs, and dumb > movies alone" > (Amiri Baraka 1999) > > ------=_Part_9402_11841642.1129636592173 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,
       There was a 'stty sane' line in my .cshrc which is causing the Invalid argument message. I removed it and that erorr message has gone away. Thanks, Pete.
    I also noticed that setting TERM env to any value is causing shell to exit. I removed the line which sets TERM env from my cshrc and I was able to access shell !!! But the warning message is still there.

 Warning: no access to tty (Bad file descriptor).
 Thus no job control in this shell.

      And setting TERM env in it is causing the shell to exit immediately. I guess this is because of tty not being allocated. From the shell in emacs when I type tty, I see...
$ tty
not a tty

      So there is no solution to the original problem yet, as removing the line which sets TERM env cannot be a permanent solution.

Sunil

On 10/18/05, Peter Dyballa <Peter_Dy= balla@web.de> wrote:

Am 18.10.2005 um 08:34 schrieb Sunil Yeddu:

> Warning: no acc= ess to tty (Bad file descriptor).
> Thus no job control in this shell= .
> stty: standard input: Invalid argument           &= nbsp;    <<<<<<<<<<<> exit
>
> Process shell finished

This is very fami= liar for me on Mac OS X. Here it's found that using
ttys is not reliable= . (setq process-connection-type t) in .emacs
'corrects' this.

Your problem is that some shell rc file writes = something into /dev/tty
or such without first checking whether it's allo= wed or useful. So check
the code in your shell's rc file(s), for example= make the shell
verbosely list what it's doing during its initialisation while working<= br>on the rc file(s)!

--
Greetings

   Pete
"One cannot live by television, video games, top ten CDs, and dumb
mov= ies alone"
       (Amiri Baraka 1999)

------=_Part_9402_11841642.1129636592173-- --===============1056609489== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Help-gnu-emacs mailing list Help-gnu-emacs@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnu-emacs --===============1056609489==--