9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Friedrich Psiorz <f.psiorz@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme: spaces in file names
Date: Sun, 15 Dec 2013 18:51:08 +0100	[thread overview]
Message-ID: <52ADEC0C.1000109@gmx.de> (raw)
In-Reply-To: <CABwHSOtyzmOMRj7aAcJr_ti2rXJK98QS3pCKRV2MzidyrGAZUw@mail.gmail.com>

To run the plumber, type
plumber &

then you can copy the rules file to $HOME/lib/plumbing and modify it as
you wish. The next time you start the plumber (or when you write the
modified file back via 9p), it will load that config file and hopefully
behave as you planned.

Okay, now what's the plumber? There are two kinds of Buttor-3 actions in
acme:
1) if you use button 3 on things like file names, addresses, etc. it
does some special action
2) otherwise, search text

The plumber (when running) is there to find out, if there is a special
action to perform, and then do it. Read the paper "Plumbing and other
utilities" to get more details.

~Fritz

Am 15.12.2013 17:38, schrieb Blake McBride:
> I would greatly appreciate it if you could give me the specifics on this.
>
> Thanks!
>
> Blake
>
>
>
> On Sun, Dec 15, 2013 at 10:26 AM, Friedrich Psiorz <f.psiorz@gmx.de
> <mailto:f.psiorz@gmx.de>> wrote:
>
>     To use the plumber, you have to start it first. Then you can configure
>     all the Button-3 behavior you want. No need to change the hard coded
>     backup behavior.
>
>     Am 15.12.2013 17:19, schrieb Blake McBride:
>     > Blake-Mac-17:tmp blake$ 9p read plumb/rules
>     > 9p: mount: dial unix!/tmp/ns.blake._tmp_launch-nvfpC3_org.x:0/plumb:
>     > connect /tmp/ns.blake._tmp_launch-nvfpC3_org.x:0/plumb: No such file
>     >
>     > I don't have to do this when I search for text with spaces, or to
>     > execute a command with spaces.  Not being able to load files or
>     > directories with spaces is, and I mean this in the most
>     respectfull way,
>     > short sighted and inconsistent IMO.  As long as a fix doesn't
>     limit some
>     > existing functionality, I think it should be corrected.  I am
>     qualified
>     > to make such a correction but, not being familiar with the code, I
>     > estimate it would take me a whole day to do.  I'd bet it would take
>     > someone famaliar with the code an hour.  My time, like all of
>     yours, is
>     > very limited.  I will make the change when my time permits.  My
>     hope is
>     > that someone more familiar with the code can make it before then.
>     >
>     > Thanks.
>     >
>     > Blake
>     >
>     >
>




  reply	other threads:[~2013-12-15 17:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 18:17 Blake McBride
2013-12-12 16:53 ` Robert Raschke
2013-12-12 17:00   ` Rubén Berenguel
2013-12-12 21:10     ` Blake McBride
2013-12-15 15:25       ` Blake McBride
2013-12-15 15:38         ` Friedrich Psiorz
2013-12-15 16:19           ` Blake McBride
2013-12-15 16:26             ` Friedrich Psiorz
2013-12-15 16:38               ` Blake McBride
2013-12-15 17:51                 ` Friedrich Psiorz [this message]
2013-12-15 17:56                   ` Blake McBride
2013-12-15 19:39                     ` andrey mirtchovski
2014-08-19 20:37                       ` Blake McBride
2014-08-20  9:03                         ` Riddler
2014-08-20 18:00                           ` Blake McBride
2014-08-21 15:32                             ` Skip Tavakkolian

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=52ADEC0C.1000109@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).