zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: PATCH: Allow using STTY= to save terminal state
Date: Wed, 19 Jan 2022 00:17:10 +0100	[thread overview]
Message-ID: <CAHYJk3ThwU2VmRgySUBH3YxAi-cOjAXrhNVXZJxox70vRF7eXA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZMm7PHmB551JNWWYbruah9LKpdmfiwzfrEGJ5M+U0Q3g@mail.gmail.com>

On 1/18/22, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Jan 18, 2022 at 2:25 PM Mikael Magnusson <mikachu@gmail.com> wrote:
>>
>> A person in IRC had issues with a command (fastlane) changing some random
>> stty settings [...]
>> it would be nice to be able to do this without having to specify a random
>> stty setting to actually change when starting the command
>
> Umm, isn't this what "ttyctl -f" is for?  What have I missed?

I remembered about STTY= existing, and its documentation does not
reference ttyctl (in fact nothing references ttyctl except for the
ttyctl entry). That said, running ttyctl -f and ttyctl -u around a
command is a bit more work than simply prepending STTY= (which
currently just causes the stty help text to be printed, which doesn't
seem very useful).

-- 
Mikael Magnusson


  reply	other threads:[~2022-01-18 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 22:24 Mikael Magnusson
2022-01-18 22:27 ` Bart Schaefer
2022-01-18 23:17   ` Mikael Magnusson [this message]
2022-01-19  1:10     ` Bart Schaefer
2022-01-19 14:06     ` Daniel Shahaf
2022-01-19 17:29       ` Bart Schaefer
2022-01-19 20:08         ` Peter Stephenson
2022-01-21  7:11           ` Daniel Shahaf
2022-01-22 22:44             ` Bart Schaefer

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=CAHYJk3ThwU2VmRgySUBH3YxAi-cOjAXrhNVXZJxox70vRF7eXA@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).