From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: dominik.vogt@gmx.de, Zsh-Users List <zsh-users@zsh.org>
Subject: Re: less with subprocess
Date: Thu, 30 Sep 2021 23:03:21 +0200 [thread overview]
Message-ID: <CAP+y1xBS+3mKUOaW27ao7=bP+LSkSp4JU=9ZQsBz=sVwnUA-fg@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xCVePc=3zKJeAuY0Z2Q0dO+42D78Jm6DN8dB4cpbnqgSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
Besides, google have sent me this error message two times:
The recipient server did not accept our requests to connect. Learn
more at https://support.google.com/mail/answer/7720
[prometheus.u-strasbg.fr
<https://support.google.com/mail/answer/7720%5Bprometheus.u-strasbg.fr>
130.79.203.100: FAILED_PRECONDITION: connect error (111): Connection
refused]
(of course the linked support page is inexistent...)
for a mail I tried to send to this thread, here it is again:
Date: Tue, 28 Sep 2021 22:10:04 +0200
Subject: Re: quoting words
Hello, here is the output:
5.8
a isa array
typeset -a omz=( 'the first' 'the last' )
'the first' 'the last'
the result from your script is in fact correct if I assign the
"${(@qq)omz}":
typeset -a omz=( 'the first' 'the last' )
a="${(@qq)omz}"
typeset -p a
typeset a='''the first'' ''the last'''
regards
Pier Paolo Grassi
Pier Paolo Grassi
Il giorno gio 30 set 2021 alle ore 22:59 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:
> writing on disk it can eat away all the space I have on my device and make
> other processes that need that disk space to fail. Even if disk is cheap
> doesn't mean it's always plentifully available
>
> Pier Paolo Grassi
>
>
> Il giorno gio 30 set 2021 alle ore 21:50 Dominik Vogt <dominik.vogt@gmx.de>
> ha scritto:
>
>> On Thu, Sep 30, 2021 at 09:17:06PM +0200, Vincent Lefevre wrote:
>> > 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.
>>
>> But ... even if you never press "F" in less to read the rest of
>> the input it's going to be stored somewhere, either in memory or
>> on disk. What's the point in worrying bout temporry disk space?
>>
>> Ciao
>>
>> Dominik ^_^ ^_^
>>
>> --
>>
>> Dominik Vogt
>>
>>
[-- Attachment #2: Type: text/html, Size: 4515 bytes --]
next prev parent reply other threads:[~2021-09-30 21:04 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 [this message]
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+y1xBS+3mKUOaW27ao7=bP+LSkSp4JU=9ZQsBz=sVwnUA-fg@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).