From: Eduardo Alvarez <astrochelonian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Plumbing - Files with spaces
Date: Wed, 22 Jul 2015 10:20:48 -0300 [thread overview]
Message-ID: <CAOQs9Y3oABex2cnOwAxbt1+6GQ4_VSisfcCVNeDjD_SxNDmiOw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hello, all,
I've recently been introduced to plan9port, and have been fiddling about
with the plumber. As a test, I tried using the plumber to open several
different files wherever I specified. I noticed, however, that I was unable
to plumb files whose names had spaces in them. A search on google on the
subject threw as the only solution "use shorter filenames". Fair enough,
but I wanted to know if this is a limitation of the plumber itself, or if
the regular expressions used can accomodate for spaces.
Regards,
Eduardo Alvarez
[-- Attachment #2: Type: text/html, Size: 632 bytes --]
next reply other threads:[~2015-07-22 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:20 Eduardo Alvarez [this message]
2015-07-22 13:29 ` dexen deVries
2015-07-22 14:07 ` erik quanstrom
2015-07-22 15:13 ` Friedrich Psiorz
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=CAOQs9Y3oABex2cnOwAxbt1+6GQ4_VSisfcCVNeDjD_SxNDmiOw@mail.gmail.com \
--to=astrochelonian@gmail.com \
--cc=9fans@9fans.net \
/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).