9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jon Dugan <jdugan@x1024.net>
To: 9fans@9fans.net
Subject: [9fans] Export local plumber to remote unix host?
Date: Wed, 27 Aug 2008 01:02:02 -0700	[thread overview]
Message-ID: <1219823269-sup-1399@neocybil.x1024.net> (raw)

Hello,

I read my email on a remote Unix machine which I access from a few terminals
via ssh.  The terminals are also Unix hosts (usually OS X). This works great
for reading text.  However, I frequently receive attachements.  What I'd like
to be able to do is export at least my plumber over the ssh connection to the
remote host so I can display the attachments locally.  This seems to be the
opposite of what import(1) does.  I guess what I want is cpu(1) for
plan9port...  or at least a limited version of it.

This seems like it should be doable, but I think I'm looking at it the wrong
way.

Any suggestions?  (Unfortunately the Unix boxes and Word documents aren't
going away any time soon for me...)

Thanks,

Jon



             reply	other threads:[~2008-08-27  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  8:02 Jon Dugan [this message]
2008-08-27 15:57 ` sqweek
2008-08-27 16:11   ` erik quanstrom
2008-08-27 16:53   ` sqweek
2008-08-27 17:53 ` a

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=1219823269-sup-1399@neocybil.x1024.net \
    --to=jdugan@x1024.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).