From: "népéta mew" <nepeta@canaglie.net>
To: 9front@9front.org
Subject: [9front] plumbing with spaces
Date: Wed, 06 Nov 2024 12:15:30 +1100 [thread overview]
Message-ID: <32ERPD9FSEHN0.2PR9UYWTR5B74@canaglie.net> (raw)
hi there. it's Me.
i've noticed that plumbing files with spaces in their name
tends to be somewhat janky, i think because the plumber expands
the spaces before executing an rc command in plumb start.
so:
a. what's the best way of working around this?
is surrounding a $file with a bunch of quotes in the rc command
the best solution, or is there a better solution?
b. maybe Upgrading the plumber to somehow deal nicely with spaces
would be useful? i dunno.
thank you for reading this is the end of the e mail good bye
next reply other threads:[~2024-11-06 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:15 népéta mew [this message]
2024-11-06 4:57 ` umbraticus
2024-11-06 12:40 ` hiro
2024-11-07 8:46 ` umbraticus
2024-11-07 8:52 ` umbraticus
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=32ERPD9FSEHN0.2PR9UYWTR5B74@canaglie.net \
--to=nepeta@canaglie.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).