From: Luc Henninger <luc.henninger@orange.fr>
To: cygwin@cygwin.com
Subject: Re: Re: Issue with mintty: title not updated when background process exists
Date: Wed, 1 Apr 2020 22:21:40 +0200 [thread overview]
Message-ID: <5df553fb-45cd-f228-c533-69a5db6e81be@orange.fr> (raw)
In-Reply-To: <0f8c0f14-f978-c487-5702-0fc8a6727ce5@towo.net>
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
Le 01/04/2020 à 14:24, Thomas Wolff a écrit :
> Am 01.04.2020 um 14:20 schrieb Thomas Wolff:
>> Am 01.04.2020 um 13:07 schrieb Luc Henninger:
>>> Hello,
>>>
>>> I have defined the PS1 variable as follow
>>> PS1='\[\e]0;\w\a\]\[\e[32m\]\u@\h \[\e[35m\]\w\[\e[0m\]\n\$ '
>>> so that the cur dir is set as title of the window.
>>>
>>> This generally work for both mintty or cmd.
>>> But after the sequence
>>> Luc@Mulan ~
>>> $ emacs &
>>> [1] 371
>>> Luc@Mulan ~
>>> $ cd bin
>>> Luc@Mulan ~/bin
>>> $
>>> the title of the mintty widow remain to "~".
>>>
>>> The same sequence with cmd window change the title to "~/bin"
>>>
>>> The title is correctly updated only after I close emacs and push a
>>> return to the main window.
>>>
>>> Any explanation? Thanks
>> Noted first, this is in any case not a mintty issue as mintty updates
>> the title whenever it receives the respective escape sequence. The
>> scenario sounds weird, however. Is the background process
>> continuously sending title escape sequences? But 'emacs &' looks like
>> you're starting a GUI instance of emacs, right? So why should it?
> Try to isolate the background instance from the terminal:
> emacs > /dev/null 2>&1 &
>
Even if your proposal solve the issue, I have a question of what's
append in the two different cases.
I use the same sequence (1/ cd ztry 2/ launch emacs ("emacs &" or "emacs
> /dev/null 2>&1 &" 3/ cd .. 4/ exit emacs 5/ newline 6/ ^D) with
mintty configure for logs.
The log for the first case (mintty1459.log) is strongly longer that the
second one (mintty1470.log). It look like the wall window content is
rewritten each time a line is added.
I would appreciate if someone can give me some explanation. It look like
that I have the same kind of behavior with other program (i.e. scala
repl or sbt)
Thanks
--
Luc.Henninger@orange.fr +33 6 32 96 32 27
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
[-- Attachment #2: mintty1459.log --]
[-- Type: application/octet-stream, Size: 1467 bytes --]
[-- Attachment #3: mintty1470.log --]
[-- Type: application/octet-stream, Size: 371 bytes --]
next prev parent reply other threads:[~2020-04-01 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 11:07 Luc Henninger
2020-04-01 12:20 ` Thomas Wolff
2020-04-01 12:24 ` Thomas Wolff
2020-04-01 19:44 ` Luc Henninger
2020-04-01 20:21 ` Luc Henninger [this message]
2020-04-01 21:54 ` Thomas Wolff
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=5df553fb-45cd-f228-c533-69a5db6e81be@orange.fr \
--to=luc.henninger@orange.fr \
--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).