From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: check if coproc has output
Date: Thu, 19 Jan 2023 16:36:29 +0000 [thread overview]
Message-ID: <CAKc7PVBzaRDJyLCpMxv2Gu02GNvN2gRjq2kvx3cRY37f1Oce-w@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xB2o-09v1TEV8M=e_S=Xe9sdkXLs6sSpN5srPtZnX39jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]
I've read your post briefly and saw that you need to terminate the
background process. I recall that I was doing it in configure-wrapper that
I once wrote and that I used jobtexts. I do recall that it does contain
entry for coproc, so you could examine it in a INT trap and send a signal
to the coproc writing process.
On Thu, 19 Jan 2023 at 16:14, Pier Paolo Grassi <pierpaolog@gmail.com>
wrote:
> I did again the search in the manual and now I found it, maybe I mistyped
> the first time
> where do you suggest I try to print this array?
>
> Pier Paolo Grassi
>
>
> Il giorno gio 19 gen 2023 alle ore 17:10 Sebastian Gniazdowski <
> sgniazdowski@gmail.com> ha scritto:
>
>> Are you running zsh 3.0? That would only explain lack of following in
>> zshall:
>>
>> jobtexts
>> This associative array maps job numbers to the texts of the
>> command
>> lines that were used to start the jobs.
>>
>> Handling of the keys of the associative array is as
>> described for
>> jobdirs above.
>>
>>
>> On Thu, 19 Jan 2023 at 16:08, Pier Paolo Grassi <pierpaolog@gmail.com>
>> wrote:
>>
>>> I'm sorry, what is $jobtexts? it seems an empty variable to me and
>>> doesn't appear in zshall manual
>>>
>>> Pier Paolo Grassi
>>>
>>>
>>> Il giorno gio 19 gen 2023 alle ore 17:02 Sebastian Gniazdowski <
>>> sgniazdowski@gmail.com> ha scritto:
>>>
>>>> You could get pid from $jobtexts?
>>>>
>>>> On Thu, 19 Jan 2023 at 15:43, Pier Paolo Grassi <pierpaolog@gmail.com>
>>>> wrote:
>>>>
>>>>> I realize now the subject doesn't reflect the final version of the
>>>>> mail, sorry for that
>>>>>
>>>>> Pier Paolo Grassi
>>>>>
>>>>>
>>>>> Il giorno gio 19 gen 2023 alle ore 16:32 Pier Paolo Grassi <
>>>>> pierpaolog@gmail.com> ha scritto:
>>>>>
>>>>>> Hello, I want to populate an array from a long running process,
>>>>>> something like:
>>>>>>
>>>>>> long_running_process | while read line
>>>>>> do
>>>>>> array+=$line
>>>>>> done
>>>>>>
>>>>>> problem is, since long_running_process does not continually produce
>>>>>> output but only some times, when i try to interrupt this pipeline with
>>>>>> ctrl-c I have to wait until it produces some output for the process to
>>>>>> terminate (because, as I understand it, when it tries to write to the pipe
>>>>>> it receives a sigpipe due to it being already closed)
>>>>>>
>>>>>> I have tried various constructs with trap and even coproc to be able
>>>>>> to intercept the ctrl-c and send a sigpipe to the long running process, but
>>>>>> to no result.
>>>>>>
>>>>>> I wonder if someone has some solution to share for this problem,
>>>>>> thanks
>>>>>>
>>>>>> Pier Paolo Grassi
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Sebastian Gniazdowski
>>>>
>>>>
>>
>> --
>> Best regards,
>> Sebastian Gniazdowski
>>
>>
--
Best regards,
Sebastian Gniazdowski
[-- Attachment #2: Type: text/html, Size: 5927 bytes --]
next prev parent reply other threads:[~2023-01-19 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 15:32 Pier Paolo Grassi
2023-01-19 15:42 ` Pier Paolo Grassi
2023-01-19 16:01 ` Sebastian Gniazdowski
2023-01-19 16:08 ` Pier Paolo Grassi
2023-01-19 16:09 ` Sebastian Gniazdowski
2023-01-19 16:13 ` Pier Paolo Grassi
2023-01-19 16:36 ` Sebastian Gniazdowski [this message]
2023-01-19 16:53 ` Pier Paolo Grassi
2023-01-19 16:02 ` Roman Perepelitsa
2023-01-19 16:24 ` Pier Paolo Grassi
2023-01-19 16:33 ` Roman Perepelitsa
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=CAKc7PVBzaRDJyLCpMxv2Gu02GNvN2gRjq2kvx3cRY37f1Oce-w@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=pierpaolog@gmail.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).