From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Update hpost to use -r header like hget
Date: Wed, 16 Dec 2020 22:55:50 +0000 (UTC) [thread overview]
Message-ID: <2b7ef049-b2ea-46ab-9630-d6bdba2000a3@sirjofri.de> (raw)
In-Reply-To: <0F525CBFB1204B0572F197D1BC37058A@eigenstate.org>
There were several misunderstandings:
16.12.2020 22:52:11 ori@eigenstate.org:
> Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
>>
>> The whole thing is indeed an interesting challenge, especially because
rc
>> is handling items and lists so special. Spaces don't necessarily
separate
>> strings, items with spaces are not always quoted, etc. For example,
the
>> visual string "this is a string" is not always a list with 3 strings.
It
>> could also be a list with two or only one string.
>
> there's no sometimes about it, and there aren't any funny rules.
>
> rc never requotes something behind your back; it parses it once,
> and keeps it parsed. evaluating the output of `{} is the place
> where it parses it.
>
> All other times, it stays split.
>
>> "this is a string" is not always a list with 3 strings.
I used "" to quote it in the english text, not for rc. I maybe should
have pointed that out.
> no, that's always a string with 4 strings:
>
> '"this'
> 'is'
> 'a'
> 'string"'
Sure. Four. I should learn counting again...
> Note that " is not a special character, so it doesn't
> affect string splitting. I suspect you meant
>
> 'this is a string'
>
> which is *always* a single string to rc.
Note that I was talking about the 'visual' appearance, like, what you get
when echoing the list/variable or 'what you see on the screen'. When you
see the string "this is a string" (without the '"') on the screen inside
your window as an output there's no way to know how long the list is.
I guess even when capturing the output with `{...} it is still impossible
to know that, because then rc is reevaluating the string into a list.
next prev parent reply other threads:[~2020-12-16 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 18:02 Julien Blanchard
2020-12-15 18:42 ` ori
2020-12-16 18:16 ` Julien Blanchard
2020-12-16 18:51 ` sirjofri
2020-12-16 19:50 ` ori
2020-12-16 21:34 ` sirjofri
2020-12-16 21:52 ` ori
2020-12-16 22:55 ` sirjofri [this message]
2020-12-16 23:13 ` Steve Simon
2020-12-17 9:33 ` Julien Blanchard
2020-12-17 10:30 ` Alex Musolino
2020-12-17 11:23 ` Julien Blanchard
2020-12-18 4:35 ` ori
2020-12-16 19:54 ` estevan.cps
2020-12-18 2:25 ` magma698hfsp273p9f
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=2b7ef049-b2ea-46ab-9630-d6bdba2000a3@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.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.
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).