public inbox for
help / color / mirror / Atom feed
From: Mark Hansen <meh@Winfirst.Com>
Subject: Re: Problem launching XTerm on new Cygwin installation
Date: Sat, 08 Mar 2014 00:43:00 -0000	[thread overview]
Message-ID: <531A67C6.9000502@Winfirst.Com> (raw)
In-Reply-To: <>

On 3/7/2014 4:36 PM, Thomas Dickey wrote:
> On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote:
>> Okay, this is very strange. As I said before, I have had no problems launching XTerms
>> on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems
>> ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began
>> having the same problem I saw on the laptop (the error having to do with XTERM_SHELL).
>> I edited the launcher shortcut to remove the "/bin/zsh -l" from the end of the command
>> and it started working again.
>> I didn't do anything to update the Cygwin product on my desktop during this time.
> xterm handles these three cases differently:
> 	xterm
> 	xterm /bin/zsh
> 	xterm -e /bin/zsh
> The bug that I mentioned is in the second case - not in the other two.

Thanks. That was the bug I hit on my laptop. However, my desktop PC was working
fine with "xterm ... /bin/zsh -l" and then suddenly, it started getting the same
error. I made the same change to it as I did on my laptop PC and it worked, so
I'm not stopped - I'm just wondering how my desktop PC was working then suddenly
stopped working without altering any of the Cygwin software or settings.

Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-03-08  0:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 19:57 Mark Hansen
2014-03-07 21:50 ` Thomas Dickey
2014-03-07 22:04   ` Mark Hansen
2014-03-07 22:12     ` Thomas Dickey
2014-03-07 23:37       ` Mark Hansen
2014-03-08  0:36         ` Thomas Dickey
2014-03-08  0:43           ` Mark Hansen [this message]
2014-03-07 22:00 ` Mark Hansen
2014-03-16 18:48 ` Mark Hansen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=531A67C6.9000502@Winfirst.Com \ \ \

* 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).