From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rc: null list in concatenation line numbers
Date: Wed, 28 Oct 2020 10:50:52 +0100 [thread overview]
Message-ID: <5BA9B16CBB71B4BD72D0102880168689@felloff.net> (raw)
In-Reply-To: <BC4EEF3837ACB3DFAD9BF3E15311D7E3@eigenstate.org>
> Here's another iteration. It also handles /env/fn#foo,
> and uses \n as the line separator for /env/fn#foo so
> that we have some useful line numbers.
i wonder if this breaks "whatis fuction".
this is also used in rcpu to serialize the rc functions
to the remote side...
there might be programs that only expect single line
output?
--
cinap
next prev parent reply other threads:[~2020-10-28 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 1:40 ori
2020-10-16 3:43 ` [9front] " Xiao-Yong Jin
2020-10-17 1:47 ` ori
2020-10-16 5:40 ` Iruatã Souza
2020-10-22 1:18 ` ori
2020-10-22 12:11 ` tlaronde
2020-10-25 20:29 ` ori
2020-10-25 23:18 ` cinap_lenrek
2020-10-26 1:00 ` ori
2020-10-25 23:41 ` cinap_lenrek
2020-10-26 1:33 ` ori
2020-10-26 7:36 ` cinap_lenrek
2020-10-28 3:16 ` ori
2020-10-28 9:50 ` cinap_lenrek [this message]
2020-10-28 17:59 ` ori
2020-10-31 1:55 ` ori
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=5BA9B16CBB71B4BD72D0102880168689@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).