public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Problem with xterm-301-1
Date: Thu, 20 Feb 2014 18:33:00 -0000	[thread overview]
Message-ID: <CAK-n8j7t5WBfPhSx8+Cn2HXC6Zpp7jFDH84bQHyva-WGC=5PWg@mail.gmail.com> (raw)
In-Reply-To: <53063FA4.5020806@gmail.com>

On Thu, Feb 20, 2014 at 10:47 AM, Ola Strömfors wrote:

> After updating from 291-1 to 301-1 xterm starts /bin/sh instead of
> my shell specified in /etc/passwd or in the SHELL environment variable.

I saw the same thing, but only on my home computer running Windows 7
Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit.

I start Xwin this way (i.e. same as Cygwin-X group in Start menu):

    C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe

I don't know why SHELL defined as /bin/sh by default (my entry in the
/etc/passwd file invokes bash).  I could not find a way to change
SHELL before XWin starts.

One way I fixed it was to launch xterm from .XWinrc like this:

        "xterm"      EXEC  "xterm -e /bin/bash"

instead of this:

        "xterm"      EXEC  "xterm -ls"

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2014-02-20 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 17:47 Ola Strömfors
2014-02-20 18:33 ` Jim Reisert AD1C [this message]
2014-02-20 21:58   ` Thomas Dickey
2014-02-20 18:45 ` Matt Seitz (matseitz)
2014-02-20 22:40   ` Thomas Dickey
2014-02-27 18:06     ` Matt Seitz (matseitz)
2014-02-27 22:00       ` Thomas Dickey
2014-02-28  9:19         ` Corinna Vinschen

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='CAK-n8j7t5WBfPhSx8+Cn2HXC6Zpp7jFDH84bQHyva-WGC=5PWg@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --cc=cygwin-xfree@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).