public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tomi Belan <tomi.belan@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Long window title escape sequence breaks console output
Date: Sat, 18 Jun 2022 17:56:05 +0200	[thread overview]
Message-ID: <CACUV5ocy-cWwaj72HFcPiQQkto=yz1o9-FLvTaYsM28cRzmJsw@mail.gmail.com> (raw)
In-Reply-To: <CACUV5ofVqAs37Fv1uzAkCNTSQtm0-5BxQ01UyCWWUss-MBTUpg@mail.gmail.com>

On Fri, Jun 17, 2022 at 3:38 PM Tomi Belan <tomi.belan@gmail.com> wrote:
> I hope you enjoyed the bug report. Let me know if you have any questions.
>
> Tomi

Takashi Yano wrote:
> Thanks for the report. What situation do you assume where
> such a long title needs to be set?

I experienced the bug because my shell is configured to print the
currently running command in the window title. When I ran a command
longer than 256 characters, it looked like the command didn't run. It
actually did run, but ssh.exe ate its output.

Example: https://tldp.org/HOWTO/Xterm-Title-5.html (but I'm not using zsh)

I know this isn't a common configuration, but I still hope you'll fix
it. Since cygwin just uses mailing lists instead of a real persistent
bug tracker, I'm worried about the bug being forgotten forever if it's
not fixed soon.

Truncating the title to 256 WITH the final '\a' is a suboptimal but
acceptable fix. A better idea might be: in non-legacy terminals, don't
even switch from "normal" to "gettitle", just print everything as it
arrives.

I'm not subscribed to the mailing list so I'm manually sending this as
a reply to my first email. Sorry for the mess. Please CC me on future
replies.

  parent reply	other threads:[~2022-06-18 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 13:38 Tomi Belan
2022-06-17 20:11 ` Takashi Yano
2022-06-18 15:56 ` Tomi Belan [this message]
2022-06-19  4:16   ` Takashi Yano
2022-06-19 11:24     ` Tomi Belan

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='CACUV5ocy-cWwaj72HFcPiQQkto=yz1o9-FLvTaYsM28cRzmJsw@mail.gmail.com' \
    --to=tomi.belan@gmail.com \
    --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).