From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Peter Stephenson <p.w.stephenson@ntlworld.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: stdbuf -o0 -i0 via a Zsh native interface?
Date: Fri, 26 May 2023 11:30:27 +0200 [thread overview]
Message-ID: <CAN=4vMoONEB5saZMUutyy7jKM16EXT2k00nfrhxrU1BkzvFi5Q@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCK0MFvGmgYxzKf3+_3iktOx-6ivbB98YyxK4mPTZkU+Q@mail.gmail.com>
On Fri, May 26, 2023 at 11:24 AM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> I've took a look, and it seems to be easy:
> 1. Export LD_PRELOAD=/usr/lib/zsh/5.7/libzstdbuf.so
> - https://github.com/coreutils/coreutils/blob/master/src/stdbuf.c#L196
> - https://github.com/coreutils/coreutils/blob/master/src/stdbuf.c#L259
> 2. Provide stdbuf function in libzstdbuf.so:
> - https://github.com/coreutils/coreutils/blob/master/src/libstdbuf.c#L139
>
> Seems fairly simple…
This won't work reliably. E.g., it may not work on binaries that are
linked against a different libc. A more reliable solution for your
problem is something like `unbuffer` from `expect`. This tool creates
a TTY and takes advantage of the convention that stdout to TTY is not
buffered. Better yet, you can do this with zpty without external
tools.
Roman.
next prev parent reply other threads:[~2023-05-26 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 11:21 Sebastian Gniazdowski
2023-05-25 14:16 ` Peter Stephenson
2023-05-25 18:35 ` Bart Schaefer
2023-05-25 19:02 ` Sebastian Gniazdowski
2023-05-25 19:09 ` Bart Schaefer
2023-05-25 19:28 ` Sebastian Gniazdowski
2023-05-25 21:21 ` Bart Schaefer
2023-05-26 2:17 ` Sebastian Gniazdowski
2023-05-26 10:23 ` Sebastian Gniazdowski
2023-05-26 9:30 ` Roman Perepelitsa [this message]
2023-05-26 20:52 ` Bart Schaefer
2023-05-30 11:17 ` Peter Stephenson
2023-05-31 12:38 ` Sebastian Gniazdowski
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='CAN=4vMoONEB5saZMUutyy7jKM16EXT2k00nfrhxrU1BkzvFi5Q@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=schaefer@brasslantern.com \
--cc=sgniazdowski@gmail.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).