From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tiny & convenient change for /acme/mail/Mail
Date: Thu, 20 Jun 2002 14:15:32 +0200 [thread overview]
Message-ID: <e7f2ad32741e6e6b44973ac003711163@plan9.escet.urjc.es> (raw)
> as you can usually use the attachment directly (noting that upas/fs will
> accept any file extension on "body"). at least that way you avoid
Didn't notice it.
>
> you can plumb the attachments directly too (just as long as upas/fs
> was started before the plumber); mind you, it's a bit strange that you
I was starting them in the wrong order. ugh.
This makes /usr/nemo/attach better than /tmp/attach, since the
only time I'm likely to execute the command is when I decide to
save it and that would require just the insertion of text between
/usr/nemo and the file name.
thanks a lot
next reply other threads:[~2002-06-20 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 12:15 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 15:43 Russ Cox
2002-06-20 15:37 Russ Cox
2002-06-20 11:55 rog
2002-06-20 7:33 Fco.J.Ballesteros
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=e7f2ad32741e6e6b44973ac003711163@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).