9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] htmlfs
Date: Tue, 31 Aug 2021 12:36:18 +0200	[thread overview]
Message-ID: <CAFSF3XMktweESBSz-9Y_=Y_Aspd0uYXL2J6Ni+hmFhPW1kZNZQ@mail.gmail.com> (raw)
In-Reply-To: <A3A80A17-AC98-4A07-B88F-1B4795B3B5D7@jstsmthrgk.eu>

i can confirm, but the man page doesn't represent the ideas.

if you end up using this, you will see that for each element one line
of text is printed, including the full path/name of the value.

it feels a little bit like the output of grep -r, just with xml
hierarchy instead of file paths.

i always thought it would be neat to have a real fs instead, allowing
globbing instead of grep to read a specific element.

example:

$ html2 < poettering-Walkthrough\ for\ Portable\ Services.html
2>/dev/null | grep head/title
/html/head/title= Walkthrough for Portable Services

would be cool to instead run:
; htmlfs poettering*html
mounted at /n/htmlfs
; cat /n/htmlfs/*/*/title
Walkthrough for Portable Services
;

cool.
but not necessary for my use case.

A file is useful for separating binary data and strings that contain
newlines, but it just so happens that inside html you can often ignore
newlines, which means that practically the value of any entity should
fit quite well on a line of text as html2/xml2 output it.

On 8/31/21, jstsmthrgk <jstsmthrgk@jstsmthrgk.eu> wrote:
> There exists a piece of software (for linux) with some interesting ideas
> regarding xml scriptability:
> https://manpages.debian.org/unstable/xml2/html2.1.en.html
>
>
> Am 31. August 2021 07:33:25 MESZ schrieb unobe@cpan.org:
>>Quoth Amavect <amavect@gmail.com>:
>>> Not everything needs to be a file system.
>>> A program still needs to deserialize and load structs.
>>> A 9p fs just doesn't do that.
>>
>>That's true, there are benefits to a programming library (namely,
>>performance).  But doesn't a file system that presents a consistent
>>interface allow for a choice of programming language and for the
>>ability to abstract further?  For instance, having xmlfs (if such a
>>thing existed) would allow for rc programs to do some simple tasks
>>that need to muck with xml.
>>
>
>
>

  reply	other threads:[~2021-08-31 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 21:05 Philip Silva
2021-08-30  4:12 ` Amavect
2021-08-31  5:33   ` unobe
2021-08-31  9:46     ` jstsmthrgk
2021-08-31 10:36       ` hiro [this message]
2021-08-31 12:29         ` Steve Simon
2021-09-01  6:53           ` hiro
2021-09-01  8:30             ` sirjofri
2021-09-01  9:02               ` kvik
2021-08-31 20:09     ` hiro
2021-08-31 22:40       ` Stuart Morrow
2021-08-31 11:49   ` hiro
2021-08-31 15:42     ` Philip Silva
2021-08-31  5:23 ` unobe
2021-08-31 13:20 ` Pavel Renev
2021-08-31 15:40   ` Philip Silva
2021-09-02 11:44   ` hiro
2021-09-02 12:32     ` 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='CAFSF3XMktweESBSz-9Y_=Y_Aspd0uYXL2J6Ni+hmFhPW1kZNZQ@mail.gmail.com' \
    --to=23hiro@gmail.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).