public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Thomas Dickey <dickey@his.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Problem with xterm-301-1
Date: Thu, 20 Feb 2014 21:58:00 -0000 [thread overview]
Message-ID: <20140220215747.GB3983@aerie.jexium-island.net> (raw)
In-Reply-To: <CAK-n8j7t5WBfPhSx8+Cn2HXC6Zpp7jFDH84bQHyva-WGC=5PWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Thu, Feb 20, 2014 at 11:33:22AM -0700, Jim Reisert AD1C wrote:
> 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
That sounds like a case reported Saturday - see
ftp://invisible-island.net/temp/xterm-301a.patch.gz
I have a few other reports on different issues to iron out, and
expect to be ok with #302 sometime next week.
--
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-20 21:58 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
2014-02-20 21:58 ` Thomas Dickey [this message]
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=20140220215747.GB3983@aerie.jexium-island.net \
--to=dickey@his.com \
--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).