From: rob pike <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9Term settings
Date: Wed, 4 Dec 2002 22:53:44 -0800 [thread overview]
Message-ID: <82349806.1039042424@[192.168.0.2]> (raw)
In-Reply-To: <dba54f360d7bfe3b8827f74f9f485fec@plan9.bell-labs.com>
I do even more than that. My 9fs rule looks like
srvssh ...
bind /n/machine/home /home
so that the file names I find embedded in Unix
files are plumbable.
I hope soon to have ssh windows have plumbable
names back to Plan 9. Stay tuned.
-rob
next prev parent reply other threads:[~2002-12-05 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 6:44 Russ Cox
2002-12-05 6:53 ` rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 15:29 nowayjose
[not found] <athiele@charter.net>
2002-12-01 15:26 ` Adrian
2002-12-02 0:31 ` Scott Schwartz
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='82349806.1039042424@[192.168.0.2]' \
--to=rob@mightycheese.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).