zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: stdbuf -o0 -i0 via a Zsh native interface?
Date: Thu, 25 May 2023 11:21:32 +0000	[thread overview]
Message-ID: <CAKc7PVAh95GL_kx1FiACaexEHsK8PVLrJ+T4KxnKTZr=5KDXMw@mail.gmail.com> (raw)

Hi
I'm using coproc to continuously read command's output, to have the
effect of `CMD | fzf` – i.e. of instantly available contents while
reading all of it eventually, However, I've had problem with buffering
– no output from the CMD in `coproc CMD` was available for a long
time, and I've found that `coproc { stdbuf -o0 -i0 CMD; }` helps.

However, this is sub-optimal solution because I have to hideously
prepend the stdbuf command before each user CMD, meaning that entering
builtin commands will not work (e.g.: `stdbuf -i0 -o0 print smthg`).

I wonder if the infamous buffering problem, solved by the hacky
ld-preload stdbuf program could be fixed on the level of Zsh? Like,
e.g.: special array, say: zsh_buffer=( 0 0 0 )? For stdin, stdout and
stderr buffers.

-- 
Best regards,
Sebastian Gniazdowski


             reply	other threads:[~2023-05-25 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 11:21 Sebastian Gniazdowski [this message]
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
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='CAKc7PVAh95GL_kx1FiACaexEHsK8PVLrJ+T4KxnKTZr=5KDXMw@mail.gmail.com' \
    --to=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).