From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom vs 9front
Date: Tue, 12 Mar 2013 17:18:05 -0400 [thread overview]
Message-ID: <905cb29235089931f40fabda417da409@9srv.net> (raw)
In-Reply-To: <163bf14d9d1433a4678556107abc9a93@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
Not unless I'm missing something. That makes the paths
plumbable, sure, but it doesn't hand them to Wiki (the acme
program), so you just get the directory that Wiki reads,
which isn't really the best situation.
Shouldn't be much to it.
Anthony
[-- Attachment #2: Type: message/rfc822, Size: 3007 bytes --]
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom vs 9front
Date: Tue, 12 Mar 2013 16:55:34 -0400
Message-ID: <163bf14d9d1433a4678556107abc9a93@coraid.com>
> ² It'd be neat if someone would work out how to get the
> plumber to handle /mnt/wiki paths (or some conventional
> mapping thereof) so we could pass them around as
> pseudo-hotlinks.
just need to mount wikifs in the namespace of the plumber
with Local.
- erik
next prev parent reply other threads:[~2013-03-12 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 16:22 Kyle Laracey
2013-03-11 16:36 ` erik quanstrom
2013-03-14 11:43 ` Kyle Laracey
2013-03-11 17:30 ` Richard Miller
2013-03-11 19:50 ` David du Colombier
2013-03-11 20:34 ` balaji
2013-03-11 20:36 ` Bakul Shah
2013-03-11 20:47 ` Matthew Veety
2013-03-11 20:56 ` Bakul Shah
2013-03-12 1:49 ` Lyndon Nerenberg
2013-03-12 20:53 ` a
2013-03-12 20:55 ` erik quanstrom
2013-03-12 21:18 ` a [this message]
2013-03-14 11:43 ` Kyle Laracey
2013-03-14 13:05 ` hiro
2013-03-14 13:38 ` erik quanstrom
2013-03-14 13:49 ` Kurt H Maier
2013-03-14 15:58 ` [9fans] 9front Acme unresponsive to key presses Steffen Daode Nurpmeso
2013-03-14 16:41 ` [9fans] 9atom vs 9front Bakul Shah
2013-03-14 11:43 ` Kyle Laracey
2013-03-14 11:43 ` Kyle Laracey
2013-03-14 16:08 ` Matthew Veety
2013-03-14 19:46 ` Bakul Shah
2013-03-14 11:48 ` Kyle Laracey
2013-03-11 16:32 Kyle Laracey
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=905cb29235089931f40fabda417da409@9srv.net \
--to=a@9srv.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).