From: Sunil Yeddu <ysunilraja@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: M-x shell not working
Date: Tue, 18 Oct 2005 04:56:32 -0700 [thread overview]
Message-ID: <13ecef2d0510180456p67bb4175ld3fa440af1f5390f@mail.gmail.com> (raw)
In-Reply-To: <708ac6dccd5c5bcbc601b8ebb3760da0@Web.DE>
[-- Attachment #1.1: Type: text/plain, Size: 1729 bytes --]
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_Dyballa@web.de> 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)
>
>
[-- Attachment #1.2: Type: text/html, Size: 2395 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
next prev parent reply other threads:[~2005-10-18 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 6:34 M-x shell not working Sunil Yeddu
2005-10-18 9:27 ` Peter Dyballa
2005-10-18 11:56 ` Sunil Yeddu [this message]
2005-10-18 18:28 ` Kevin Rodgers
2005-10-19 6:36 ` Sunil Yeddu
2005-10-19 9:00 ` Peter Dyballa
2005-10-19 10:43 ` Sunil Yeddu
2005-10-20 9:02 ` Peter Dyballa
[not found] ` <13ecef2d0510200309v19be5860g8d85c8ebcfd70585@mail.gmail.com>
2005-10-20 12:02 ` Fwd: " Sunil Yeddu
[not found] ` <6172b6c2efe01b4025c9d58fe9624236@Web.DE>
2005-10-20 12:03 ` Sunil Yeddu
2005-10-20 13:45 ` Eli Zaretskii
2005-10-21 12:52 ` Sunil Yeddu
2005-10-25 6:19 ` Sunil Yeddu
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=13ecef2d0510180456p67bb4175ld3fa440af1f5390f@mail.gmail.com \
--to=ysunilraja@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).