From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Zsh-Users List <zsh-users@zsh.org>, dominik.vogt@gmx.de
Subject: Re: less with subprocess
Date: Fri, 1 Oct 2021 03:32:30 +0200 [thread overview]
Message-ID: <CAP+y1xBoZ5bKJwjX1m8n25v_fvbacLEBVkAgqwEj9Qw79+G07A@mail.gmail.com> (raw)
In-Reply-To: <20211001003146.GA24071@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
I use this on production servers where i don't want to alter anything that
is't necessary, so of course i will not create ramdisks just for launching
a find command with a pager attached ;)
this leaving aside the issues with kill raised by vincent, which i didn't
yet looked into
Il giorno ven 1 ott 2021 alle 02:36 Dominik Vogt <dominik.vogt@gmx.de> ha
scritto:
> On Fri, Oct 01, 2021 at 02:04:11AM +0200, Pier Paolo Grassi wrote:
> > Hello, thanks for your insights, but I think you are kind of missing the
> > point: I am already happy with what
> >
> > less -f <(find ...)
> >
> > gives me in terms of ux. Of course the output is generated continuously
> and
> > it is stored in ram by less, having gigabytes of ram it doesn't really
> > matters how much output is produced.
> > The only upgrade I was looking for was to be able to do ctrl-c to dispose
> > of the command even when find had not yet produced enough output to make
> > less satisfied, the infamous one screenfull of text.
>
> 1) This is not an issue at all if the input comes from a regular
> file.
>
> 2) With "less -f <(<command>)" it can be solved by artificially
> generating at least a screen of output:
>
> $ less -f <(repeat $LINES; echo; <command>)
>
> > I fail to understand how it would help me to create a tmpfs and make the
> > long running process write there instead of to a pipe.
>
> There was some issue about the generating command being killed by
> ctrl-c. Storing output in a tempfile solves this, and using a
> ramdisk solves the disk space concerns.
>
> > If the process
> > doesn't produce output it will still hang the shell, doesn't it?
>
> The "alias" or "shell function" solutions would run the generating
> command in the backgroud, so the shell does not hang. Also, less
> does not hang when input comes from a regular file, even if that
> file is growing. This is a significant difference in behaviour
> from taking input from a pipe.
>
> Ciao
>
> Dominik ^_^ ^_^
>
> --
>
> Dominik Vogt
>
> --
Pier Paolo Grassi
[-- Attachment #2: Type: text/html, Size: 2775 bytes --]
next prev parent reply other threads:[~2021-10-01 1:33 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
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 [this message]
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=CAP+y1xBoZ5bKJwjX1m8n25v_fvbacLEBVkAgqwEj9Qw79+G07A@mail.gmail.com \
--to=pierpaolog@gmail.com \
--cc=dominik.vogt@gmx.de \
--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).