On Thu, Feb 27, 2014 at 06:05:48PM +0000, Matt Seitz (matseitz) wrote:
> > From: Thomas Dickey [mailto:dickey@his.com]
> > 
> > On Thu, Feb 20, 2014 at 06:45:00PM +0000, Matt Seitz (matseitz) wrote:
> > > > From: Ola Strömfors [mailto:ola.stromfors@gmail.com]
> > > >
> > > > 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.
> > > >
> > > > The workaround I have found is to create /etc/shells with a list of
> > > > permitted shells, e.g.
> > >
> > 
> > (whether xterm should use $SHELL incoming is a different issue that I
> > am reconsidering)
> 
> Is there any ETA for a resolution of this issue?

I added that to my changes for #302 yesterday, and have a couple more
issues to resolve (probably #302 will be available this weekend)

> I've been holding off on upgrading to xterm-301 because of this issue.  I'm
> not sure if there is some patch coming soon (either to xterm or adding a
> default /etc/shells to Cygwin), or if I should just plan on manually creating
> my own "/etc/shells".

With #302, this will work:

	SHELL=whatever xterm

but this is a special case (the program will run - a fix - but
will need to be in /etc/shells to have xterm set $SHELL):

	xterm whatever

-- 
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net