From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] control-F completion question
Date: Fri, 3 Oct 2008 19:42:53 +0100 [thread overview]
Message-ID: <2c42932f5bb869c19c26b58bead98222@quintile.net> (raw)
In-Reply-To: <a560a5d00810030939i7f337a84t5763d3f039ec07b5@mail.gmail.com>
rio does its magic (<ins> expanding filenames) by consulting /dev/wdir,
thus any way you can keep wdir up to date will allow <ins> to work,
(and the plumber to find files).
You can even use u9fs (or sftpfs) to connect to a unix box and ssh to
connect to a remote unix host, and plumb files (or use <ins> to expand
file names), this parses the current directory embedded in the unix
host's prompt - see rwd(1).
I have a similar system for accessing windows servers and windows workstations,
though I use my own server on the workstation rather than openssh.
-Steve
prev parent reply other threads:[~2008-10-03 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 16:39 Rudolf Sykora
2008-10-03 16:52 ` andrey mirtchovski
2008-10-03 17:11 ` Rudolf Sykora
2008-10-03 17:34 ` Federico G. Benavento
2008-10-03 17:34 ` erik quanstrom
2008-10-03 16:53 ` Nathaniel W Filardo
2008-10-03 17:32 ` erik quanstrom
2008-10-03 18:42 ` Steve Simon [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=2c42932f5bb869c19c26b58bead98222@quintile.net \
--to=steve@quintile.net \
--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).