From: Ross Boylan <ross@biostat.ucsf.edu>
To: David Conrad <DavidConrad@acm.org>
Cc: Andrey Repin <cygwin@cygwin.com>
Subject: Re: setting cygwin terminal (mintty) title from a very remote system
Date: Tue, 15 Apr 2014 00:20:00 -0000 [thread overview]
Message-ID: <1397521228.1612.34.camel@localhost> (raw)
In-Reply-To: <CAEotdw=3DkXiJAcdLc5KZjdvUAqn_xYaVcB2RUmLq1tnwBP74w@mail.gmail.com>
On Mon, 2014-04-14 at 14:19 -0400, David Conrad wrote:
> On Fri, Apr 11, 2014 at 4:00 PM, Adam Dinwoodie wrote:
> > On Fri, Apr 11, 2014 at 12:13:07PM -0700, Ross Boylan wrote:
> >>
> >> echo -ne '\e]0;Title\a'
> >>
> >
> > [The] title will stay the same if something intercepts that sequence, and it
> > will probably appear to stay the same if something resets it immediately
> > (many Bash shell prompts do just that).
> >
>
> The fact that something else might reset it *immediately after* you
> set it is really important. It can make it look like something you are
> trying doesn't work **when it actually does work**.
I agree, but I'm quite sure that's not my problem. I only have the
problem inside emacs (usually inside screen, but it doesn't seem to
matter). The title I'm seeing is from a different system, earlier in
the ssh chain. I tried it (using ], not [) and it didn't work; instead
some characters appeared in the emacs window. I also checked PS1 and
COMMAND_PROMPT; neither was generating any special characters. Setting
COMMAND_PROMPT to the echo command simply puts the characters in front
of the command line.
Ross
>
> I would suggest using a command like this to test setting it:
>
> echo -ne "\e[0;This is a test\a"; sleep 5
>
> That way, the title, if it's getting set at all, will remain set for a
> few seconds before it gets reset, so you can see it. That will allow
> you to tell the difference between a problem where the escape sequence
> is never reaching mintty because something is eating it, and one where
> the escape sequence is getting through just fine, but something, like
> the bash PS1 prompt, is immediately overwriting it.
>
> Good luck.
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-04-15 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 19:13 Ross Boylan
2014-04-11 20:00 ` Adam Dinwoodie
2014-04-14 18:19 ` David Conrad
2014-04-15 0:20 ` Ross Boylan [this message]
2014-04-12 0:49 ` Duncan Roe
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=1397521228.1612.34.camel@localhost \
--to=ross@biostat.ucsf.edu \
--cc=DavidConrad@acm.org \
--cc=cygwin@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).