public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mark Hansen <meh@winfirst.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Problem launching XTerm on new Cygwin installation
Date: Fri, 07 Mar 2014 23:37:00 -0000 [thread overview]
Message-ID: <531A5840.605@winfirst.com> (raw)
In-Reply-To: <20140307221219.GA5538@aerie.jexium-island.net>
On 3/7/2014 2:12 PM, Thomas Dickey wrote:
> On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote:
>> As a result, it is working so I'll leave it alone.
>
> :-)
>
>> >fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug.
>> >However, I was able to analyze it on Linux with valgrind...
>>
>> Well, I downloaded the Cygwin installation for my desktop last week, and downloaded
>> the Cygwin for my laptop yesterday. I guess the bug could have been introduced between
>> those times?
>
> yes - I finished #302 at the beginning of the week.
>
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.
I'm confused...
FYI.
--
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/
next prev parent reply other threads:[~2014-03-07 23:37 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 [this message]
2014-03-08 0:36 ` Thomas Dickey
2014-03-08 0:43 ` Mark Hansen
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:
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=531A5840.605@winfirst.com \
--to=meh@winfirst.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).