From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
Zsh-Users List <zsh-users@zsh.org>
Subject: Re: less with subprocess
Date: Tue, 28 Sep 2021 00:57:02 +0200 [thread overview]
Message-ID: <CAP+y1xDdPi=DHR0KNrdCRiroC-54ev8HhfPW5O+59ap1COLBSg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bCC--sF2_FGoB-B17RxGoSzcVTzRbuddqOnU_gtO=pXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
I am trying some variations based on suggestions from the page Roman linked:
(trap 'kill -PIPE 0' INT; less -f -+F <(eval "sleep 100" ))
/proc/self/fd/11 lines 1--1...skipping...
/proc/self/fd/11 lines 1--1...skipping...
/proc/self/fd/11 lines 1--1...skipping...
/proc/self/fd/11 lines 1--1...skipping...
/proc/self/fd/11 lines 1--1...skipping...
/proc/self/fd/11 lines 1--1...skipping...
the "skipping lines" is what is printed, I assume by less, when I press
ctrl-c
I can confirm that using ctrl-z and kill % is able to successfully get rid
of the process, but it seems kind of an emergency measure to me, not what I
would like to be my routine.
It seems to me that less is eating the ctrl-c, so the trap is never called,
because executing the kill -PIPE from another shell works, of course
replacing the 0 with the pid of one of the processes involved, sleep or
less doesn't matter.
So I'm starting to think this is something that can't be solved from the
shell because the shell is unable to do anything until less gives up the
control, am I right?
Pier Paolo Grassi
Il giorno lun 27 set 2021 alle ore 23:48 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:
> On Mon, Sep 27, 2021 at 2:38 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
> >
> > less -f =(find ...)
>
> Hm, never mind, interrupt kills that subprocess as well so it only
> solves half the probem.
>
[-- Attachment #2: Type: text/html, Size: 2112 bytes --]
next prev parent reply other threads:[~2021-09-27 22:58 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 [this message]
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
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+y1xDdPi=DHR0KNrdCRiroC-54ev8HhfPW5O+59ap1COLBSg@mail.gmail.com' \
--to=pierpaolog@gmail.com \
--cc=roman.perepelitsa@gmail.com \
--cc=schaefer@brasslantern.com \
--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).