From: Friedrich Psiorz <f.psiorz@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plumbing - Files with spaces
Date: Wed, 22 Jul 2015 17:13:11 +0200 [thread overview]
Message-ID: <55AFB307.6060706@gmx.de> (raw)
In-Reply-To: <CAOQs9Y3oABex2cnOwAxbt1+6GQ4_VSisfcCVNeDjD_SxNDmiOw@mail.gmail.com>
You can change your lib/plumbing file. If you add a space to the regular
expressions in the 'matches' rules it should work. Maybe you will need
to have two rules, one for making simple right clicking without
selection work in acme (no spaces in the regexp) and the other (with
spaces) to be able to select the exact filename, and plumb it, even if
it has spaces. Like so:
type   is   text
data   matches   '[a-zA-Z¡-￿0-9_\-./]+'
data   matches  Â
'([a-zA-Z¡-￿0-9_\-./]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI)'
arg   isfile   $0
plumb   to   postscript
plumb   start   9 page $file
type   is   text
data   matches   '[a-zA-Z¡-￿0-9_\-./ ]+'
data   matches   '([a-zA-Z¡-￿0-9_\-./
]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI)'
arg   isfile   $0
plumb   to   postscript
plumb   start   9 page $file
I haven't tried this though.
-Fritz
Am 22.07.2015 um 15:20 schrieb Eduardo Alvarez:
> 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
prev parent reply other threads:[~2015-07-22 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:20 Eduardo Alvarez
2015-07-22 13:29 ` dexen deVries
2015-07-22 14:07 ` erik quanstrom
2015-07-22 15:13 ` Friedrich Psiorz [this message]
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=55AFB307.6060706@gmx.de \
--to=f.psiorz@gmx.de \
--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).