From: tlaronde@polynum.com
To: 9front@9front.org
Subject: Re: [9front] rc: null list in concatenation line numbers
Date: Thu, 22 Oct 2020 14:11:15 +0200 [thread overview]
Message-ID: <20201022121115.GA41@polynum.com> (raw)
In-Reply-To: <9661591FC410B16CA272B221336B866C@eigenstate.org>
Hello,
On Wed, Oct 21, 2020 at 06:18:28PM -0700, ori@eigenstate.org wrote:
> > Testing and review welcome.
>
> Another iteration: This one caps the number of filenames
> that we put into the name table. It's pointless to past
> the name table past the maximum number of files that fit
> into the location.
FWIW, since the error I have when calling a rc script (hget(1)) from
a sh script under APE is "null list in concatenation", having something
to do with the definition of "path" been apparently empty (I have to set it
explicitely before calling hget), I tried the patches.
This queer problem under APE (in a very peculiar context because I have
been unable to find a small example reproducing the behavior) is still
there---I don't pretend the patches were to address this problem; I
simply tried them, because of the subject line "null list in concatenation",
to see if by side effect they would solve it.
Best,
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://www.kergis.com/kertex.html
http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2020-10-22 12:11 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 [this message]
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
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=20201022121115.GA41@polynum.com \
--to=tlaronde@polynum.com \
--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).