On Tue, Jul 14, 2009 at 02:35:50PM -0500, Kyle Wheeler wrote: > For reference, since people can and do rebind their keys, it's > probably better to refer to things by their function names. In this > case (as you can see from the help menu), it's <toggle-disposition>.
Okay, thanks. > You *can* automate the process, but creating a random file name is going to be > difficult. Mutt isn't set up to do that. Most folks don't want multiple inline > text parts (most of us just create a single text part). When I create a new message, mutt creates a file like: /tmp/mutt-tumbolia-1000-2303-0 Is there no way to hook into the same thing? Just to clarify, I have been using emails as a way or archiving various things that I find on the Internet. If I am archiving an image from Wikipedia, I may want to attach the image regularly, and then have two inline messages, one containing the URI the image was retrieved from, and the other containing any out-of-band metadata from the image page on Wikipedia. This might sound like an odd way to be using emails, and I'm sure it is. Hopefully though, you'll see that what I'm essentially wanting to send an email with multiple, but separate, inline messages. > You can add a line to your mailcap to handle text/plain messages that > contains a "compose=" setting, like this: > > text/plain; less; compose=emacs %s > > For a detailed explanation of that, read the mailcap man page. Interestingly enough, this only seems to half work: <new-mime>foo<enter>text/plain<enter> Emacs is fired up, editing a file at /tmp/foo, which is correct. After saving, I then do: <edit-mime> And a Vi is started, editing the correct file. Interestingly enough, if I do: <edit-file> Emacs is fired up, editing the correct file. What's going on here? What's the difference between these two commands? Thanks, -- Noah Slater, http://tumbolia.org/nslater
