public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Bug] tmux 3.2-0
Date: Mon, 31 May 2021 20:15:37 +0200	[thread overview]
Message-ID: <877djebwhi.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAALQ5r=Zx3krUx_qw-c8-_4aEsEtS63kahCZo1GzfwXpDz2B0w@mail.gmail.com> (Michael Wild via Cygwin's message of "Mon, 31 May 2021 17:37:46 +0200")

Michael Wild via Cygwin writes:
> Just out of curiosity: is this a critical feature for you? E.g. are
> you automating tmux with it? Because as far as I understand control
> mode is intended for integration with terminal emulators. And so far,
> iTerm2 on Mac is the only one implementing the protocol.

As I said in the original posting, the test suite for mosh makes use of
control mode.  Besides the terminal integration (that is non-existing on
Cygwin AFAIK) this sort of controlling terminals from scripts/automation
is probably uncommon.  GNU parallel might be using control mode too,
although I've not tried that mode and it has no official Cygwin package
either (but I use it on Cygwin).  OTOH, it is surprising that control
mode suddenly stopped working in Cygwin.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2021-05-31 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  4:54 [ANNOUNCEMENT] " Michael Wild via Cygwin-announce
2021-05-14 19:10 ` Achim Gratz
2021-05-25 20:32   ` [Bug] " Achim Gratz
2021-05-26  6:34     ` Michael Wild
2021-05-26  9:42       ` ASSI
2021-05-31 15:37         ` Michael Wild
2021-05-31 18:15           ` Achim Gratz [this message]
2021-06-02 13:22             ` Michael Wild
2021-06-02 17:38               ` Michael Wild
2021-06-03  4:56                 ` ASSI
2021-06-05  5:33                 ` ASSI
2021-06-05 15:55                   ` Achim Gratz

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=877djebwhi.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).