From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tiny & convenient change for /acme/mail/Mail
Date: Thu, 20 Jun 2002 12:55:48 +0100 [thread overview]
Message-ID: <20020620115026.E413019980@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
actually, if you're planning on using ramfs, there's not much point,
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
using up extra memory.
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
can't right click on
/mail/fs/mbox/23/1/body.gif
inside the mail message itself, but you can if you copy and paste that
text into somewhere else in acme. i think that's because upas/fs is
interpreting b3 clicks itself, and being a little too clever about it.
cheers,
rog.
[-- Attachment #2: Type: message/rfc822, Size: 1698 bytes --]
To: 9fans@cse.psu.edu
Subject: [9fans] tiny & convenient change for /acme/mail/Mail
Date: Thu, 20 Jun 2002 09:33:57 +0200
Message-ID: <6b1d728040b6ae920922201afc05a990@plan9.escet.urjc.es>
Changing /acme/mail/src/mesg.c:938
dest = egrow(estrdup(home), "/", dest);
to
dest = egrow(estrdup("/tmp"), "/", dest);
provides what IMHO is a more convenient location to copy attachments.
When using ramfs, I just copy them and don't bother to delete those that
are not of interest. For those of interest I'd edit the cp.... line
anyway to provide a correct location.
hth
next reply other threads:[~2002-06-20 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 11:55 rog [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 12:15 Fco.J.Ballesteros
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=20020620115026.E413019980@mail.cse.psu.edu \
--to=rog@vitanuova.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).