From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] [PATCH] syscall: utility overhaul
Date: Sun, 20 Sep 2020 15:13:46 +0200 [thread overview]
Message-ID: <01755B15F9510D7EA0497A5283DE2CA7@a-b.xyz> (raw)
In-Reply-To: <6c8caf6a-f5d9-4caa-97bd-90ca1269500a@www.fastmail.com>
> If a user redirects this output to a file and tries to edit it,
> sam and acme will remove the \0 bytes and issue a warning on load.
> Ed doesn't warn, but truncates lines at \0. Just raising the issue in
> case it's relevant. IMO, these are minor bugs in our editors.
This is not something that syscall(1) should worry about. If you asked
to do a syscall, then you must expect to get the result of a syscall.
> > * The -x flag is removed; the above makes it possible to pipe
> > into xd(1) to get the same result.
>
> I'm not familiar with syscall, but is it really the same result?
It's not, at least not by default. However, you can invoke xd(1) in just
the right way to get the /same/ result, if you so please.
next prev parent reply other threads:[~2020-09-20 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 13:05 kvik
2020-09-20 13:01 ` [9front] " Ethan Gardener
2020-09-20 13:13 ` kvik [this message]
2020-09-19 13:05 ori
2020-09-20 0:07 ` 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=01755B15F9510D7EA0497A5283DE2CA7@a-b.xyz \
--to=kvik@a-b.xyz \
--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).