From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/lib/plumb/basic
Date: Tue, 23 Jul 2002 00:37:40 -0400 [thread overview]
Message-ID: <3f873c4c8f97a53b4fff3b2b8bcc6751@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
I don't understand the problem. Are you saying you have two files
thread.h, in /sys/include and /3e/sys/include? And that if you plumb
<thread.h> when you're in one directory, you want to get the other?
Because I tried the following:
cd /usr/rob
date>thread.h
plumb thread.h
and the file in /usr/rob appeared in Acme, which I think is correct
behavior and is the behavior I think you ask for when you request
arg isfile ./$1 /sys/include/$1
Please explain what you expect to happen.
-rob
[-- Attachment #2: Type: message/rfc822, Size: 1677 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] /sys/lib/plumb/basic
Date: Tue, 23 Jul 2002 13:07:40 +0900
Message-ID: <890667787da841204aca0ed9983b69e5@granite.cias.osakafu-u.ac.jp>
I'm now having two different sets of include files, such as /sys/include
and /3e/sys/include. When I'm in the /3e/sys/include directory, I
cannot plumb say thread.h. How about to change the line of the
/sys/lib/plumb/basic file
from
arg isfile /sys/include/$1
to
arg isfile ./$1 /sys/include/$1.
I knwo this is a trivial thing, but changing the line so does not have
any side effect, I believe.
Kenji
next reply other threads:[~2002-07-23 4:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 4:37 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 0:40 okamoto
2002-07-23 12:29 rob pike, esq.
2002-07-23 6:41 okamoto
2002-07-23 6:37 okamoto
2002-07-23 6:24 okamoto
2002-07-23 6:58 ` Lucio De Re
2002-07-23 4:07 okamoto
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=3f873c4c8f97a53b4fff3b2b8bcc6751@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).