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, 27 Feb 2014 22:00:00 -0000 [thread overview] Message-ID: <20140227220020.GA3938@aerie.jexium-island.net> (raw) In-Reply-To: <A0DB01D693D8EF439496BC8B037A0AEF33126666@xmb-rcd-x15.cisco.com> [-- Attachment #1: Type: text/plain, Size: 1429 bytes --] 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 [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-27 22:00 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 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 [this message] 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=20140227220020.GA3938@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: linkBe 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).