public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: jelson@gmail.com
Subject: Re: xterm title setting breaks when upgrading from 32-bit to 64-bit cygwin
Date: Thu, 01 Aug 2013 17:29:00 -0000	[thread overview]
Message-ID: <51FA9AD3.2010906@dronecode.org.uk> (raw)
In-Reply-To: <CAKufN8XpKNweJUuMktWQBKeVeUL0Xj4k60RDwsnoObHf3V6pyg@mail.gmail.com>

On 01/08/2013 01:55, Jeremy Elson wrote:
> I recently upgraded from the 32-bit to the 64-bit build of Cygwin
> 1.7.22 on Windows 8 x64. For the most part, everything works
> identically (except faster!). But I have noticed one problem: xterm no
> longer seems to respond to the magic escape codes that change its
> title. My shell uses this to update the title to reflect the current
> hostname and working directory, but after the upgrade all my xterms
> just have the same title: "tcsh".
> 
> I haven't seen any mention of this bug on the mailing lists. Is anyone
> else experiencing this problem?

Thanks for pointing out this problem.

It seems that x86_64 X server has a bug that meant that no window could change
it's title after it started.

I've uploaded a snapshot at [1]. Perhaps you could try that and see if it
improves things for you?

[1] ftp://cygwin.com/pub/cygwinx/XWin.x86_64.20130801-git-beadc5a3202e096a.exe.bz2

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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/


  reply	other threads:[~2013-08-01 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  0:55 Jeremy Elson
2013-08-01 17:29 ` Jon TURNEY [this message]
2013-08-01 18:51   ` Jeremy Elson

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=51FA9AD3.2010906@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=jelson@gmail.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).