From: "Ethan A. Gardener" <eekee57@fastmail.fm>
To: Ryan Gonzalez <rymg19@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] I prefer cropping images in Plan 9
Date: Sun, 22 Jul 2018 10:27:54 +0100 [thread overview]
Message-ID: <1532251674.730116.1448792856.40E2B7D4@webmail.messagingengine.com> (raw)
In-Reply-To: <164bd6dd850.27a3.db5b03704c129196a4e9415e55413ce6@gmail.com>
On Sat, Jul 21, 2018, at 4:20 PM, Ryan Gonzalez wrote:
>
> While I'm replying here, might as well point out that, if you're going to
> do this, I think one thing that could maybe be interesting would be for the
> files to potentially contain rich data, not just plain text? Kind of like
> TempleOS or systemd's journal does.
I had some idea of structured pipes, but that idea's been on the shelf so long it's synapse-rotted. I was thinking of ls ps and others outputting key-value pairs, fields of which could then be selected by name. I suppose that would make for a relatively complex terminal, but it could also mean you could select different fields in the terminal after a slow job completes. This is somewhere in the top 5 things to work on, after the text editor and portability.
> Google Groups and Freelist are the best. Google Groups has a terrible UI
> but also has better spam filters IME.
Thanks
--
The lyf so short, the craft so long to lerne. -- Chaucer
next prev parent reply other threads:[~2018-07-22 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 13:19 Ethan A. Gardener
2018-07-21 15:20 ` Ryan Gonzalez
2018-07-21 16:17 ` hiro
2018-07-22 9:42 ` Ethan A. Gardener
2018-07-22 9:27 ` Ethan A. Gardener [this message]
2018-07-22 11:24 ` Ethan A. Gardener
2018-07-23 3:55 ` Lucio De Re
2018-07-23 7:19 ` hiro
2018-07-24 0:25 ` Steve Simon
2018-07-24 7:46 ` hiro
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=1532251674.730116.1448792856.40E2B7D4@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
--cc=rymg19@gmail.com \
/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).