From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] plumb rule for include files in different directories
Date: Tue, 11 Jun 2013 14:38:03 +0200 [thread overview]
Message-ID: <CAOCRf5VmMtZiGQiUpC3yGGVVEa8mNUu7sw0inZJ2L61G7VOUMA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
i work on a project and i'd like to be able to plumb #includes right
source files are in $path-to-project/source/$subsystem/src/
includes are in either $path-to-project/source/$subsystem/intf/
or $path-to-project/intf/$subsystem/intf/
it's quite chaothic
i'm trying (at the end of rules) with something like
type is text
wdir matches '(/path-to-project/.*)/src/.*'
arg isdir $1
data matches '([a-zA-Z¡-￿0-9]+\.h)('$addr')?'
arg isfile $dir/intf/$1
data set $file
attr add addr=$3
plumb to edit
plumb client window $editor
but it doesn't seem to work
Does anyone experimented with this (and managed to solve it)?
[-- Attachment #2: Type: text/html, Size: 1880 bytes --]
next reply other threads:[~2013-06-11 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:38 Bence Fábián [this message]
2013-06-11 14:06 ` Steve Simon
2013-06-11 16:16 ` Richard Miller
2013-06-11 16:26 ` Bence Fábián
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=CAOCRf5VmMtZiGQiUpC3yGGVVEa8mNUu7sw0inZJ2L61G7VOUMA@mail.gmail.com \
--to=begnoc@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).