From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: screen 4.0.3-5 does not respect $SHELL
Date: Wed, 13 Oct 2010 15:22:00 -0000 [thread overview]
Message-ID: <idjbb61m8t17jievd00sg9i959nogvlood@4ax.com> (raw)
In-Reply-To: <4CB5C2D1.6010702@dronecode.org.uk>
> On 12/10/2010 18:00, Andrew Schulman wrote:
> >> Initially SHELL=/bin/bash when using a link in start menu.From initial bash prompt, i start screen, fresh session. There all kinds of bash misbehavior occur, including ~/.bashrc having no effect. Apparent reason for that is that $SHELL becomes /bin/sh instead of /bin/bash within screen.
> >> A workaround is to start screen asscreen -s /bin/bashor have shell specified in .screenrc. Then bash works as expected. That screen does not respect $SHELL seems to be a bug though.
> >> Thanks to jturney from #cygwin for helping me pinpoint the problem.
> >> -anna
>
> The problem seems to be caused by the fact that bash sets SHELL, but does not
> export it by default, so screen doesn't inherit it and sets SHELL=/bin/sh.
OK, I see. And I do export SHELL in my bash startup scripts, so I don't have
this problem.
I can see two possible solutions:
(1) Tell users to export SHELL=/bin/bash if that's what they want processes
spawned by the shell to use.
(2) Add 'shell /bin/bash' into /etc/screenrc, on the theory that this should be
the default since bash is the default shell for Cygwin. Users who wanted to use
a different shell could override it in their .screenrc files.
Any thoughts on which is the better solution?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-10-13 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 16:26 Anna Z.
2010-10-12 17:00 ` Andrew Schulman
2010-10-13 14:31 ` Jon TURNEY
2010-10-13 15:22 ` Andrew Schulman [this message]
2010-10-13 15:29 ` Eric Blake
2010-10-13 15:32 ` Eric Blake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjbb61m8t17jievd00sg9i959nogvlood@4ax.com \
--to=schulman.andrew@epamail.epa.gov \
--cc=cygwin@cygwin.com \
/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).