zsh-users
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-users@zsh.org
Subject: Re: less with subprocess
Date: Thu, 30 Sep 2021 21:17:06 +0200	[thread overview]
Message-ID: <20210930191706.GA1641202@zira.vinc17.org> (raw)
In-Reply-To: <CAH+w=7an7ATJ51o-67ztFX+ShfEbrf158+Xi7OPtrm0X82vSbg@mail.gmail.com>

On 2021-09-29 07:14:23 -0700, Bart Schaefer wrote:
> On Wed, Sep 29, 2021 at 6:02 AM Vincent Lefevre <vincent@vinc17.net> wrote:
> >
> > cventin% LF () { () { cat >$1 &! less $1 ; kill $! } =(:) }
> > cventin% echo | LF
> > (anon):kill: kill 27684 failed: no such process
> 
> Yeah, if you use it with a process that produces very little output,
> the kill will fail.  But there's no point in using it in that case.

You don't always know in advance whether there will be little output.
And even with a lot of output, "kill" fails. Basically, the "cat" will
terminate as soon as the command terminates (there is no blocking due
to buffering like with a pipe).

There's another major issue: since there is no blocking, this can take
much disk space. Thus such a function must not be used in a case one
may be interested only in the beginning of the output.

> Redirect stderr of kill if this bothers you.

This won't solve the issue that "kill" may kill an arbitrary process.

I'd say that my patch on "less" provides a better solution.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


  parent reply	other threads:[~2021-09-30 19:18 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 20:30 Pier Paolo Grassi
2021-09-27 20:46 ` Roman Perepelitsa
2021-09-27 21:38   ` Bart Schaefer
2021-09-27 21:48     ` Bart Schaefer
2021-09-27 22:57       ` Pier Paolo Grassi
2021-09-27 23:05         ` Bart Schaefer
2021-09-27 23:28           ` Pier Paolo Grassi
2021-09-27 23:31         ` Dominik Vogt
2021-09-28  0:41           ` Bart Schaefer
2021-09-28  0:53             ` Bart Schaefer
2021-09-28 18:52               ` Dominik Vogt
2021-09-28 19:29                 ` Bart Schaefer
2021-09-29 13:02                   ` Vincent Lefevre
2021-09-29 13:13                     ` Pier Paolo Grassi
2021-09-29 13:26                       ` Vincent Lefevre
2021-09-29 14:14                     ` Bart Schaefer
2021-09-29 14:47                       ` Pier Paolo Grassi
2021-09-29 17:56                         ` Bart Schaefer
2021-09-30 19:22                           ` Vincent Lefevre
2021-10-01 16:44                             ` Bart Schaefer
2021-10-03  1:45                               ` Vincent Lefevre
2021-10-03 21:41                                 ` Bart Schaefer
2021-09-30 19:17                       ` Vincent Lefevre [this message]
2021-09-30 19:48                         ` Dominik Vogt
2021-09-30 20:59                           ` Pier Paolo Grassi
2021-09-30 21:03                             ` Pier Paolo Grassi
2021-09-30 22:39                               ` Bart Schaefer
2021-09-30 22:46                                 ` Pier Paolo Grassi
2021-09-30 23:46                             ` Dominik Vogt
2021-10-01  0:04                               ` Pier Paolo Grassi
2021-10-01  0:06                                 ` Pier Paolo Grassi
2021-10-01  0:31                                 ` Dominik Vogt
2021-10-01  1:32                                   ` Pier Paolo Grassi
2021-10-01  0:17                               ` Dominik Vogt
2021-10-01  2:47                               ` Vincent Lefevre
2021-09-29 12:51                 ` Vincent Lefevre
2021-09-28 19:50           ` Pier Paolo Grassi
2021-09-27 21:38 ` Dominik Vogt
2021-09-27 22:35   ` Dominik Vogt
2021-09-27 23:03     ` Bart Schaefer
2021-09-29 12:24 ` Vincent Lefevre

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=20210930191706.GA1641202@zira.vinc17.org \
    --to=vincent@vinc17.net \
    --cc=zsh-users@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).