a number of newbie questions
Greetings, mutts. I am new to mutt but old to linux; I've made the mistake of using pine up till now (past, oh, 8 years). Ug. Mutt has shown me the light. Just for the record, I despise pine because of their lack of willingness to support the Maildir format. Slackers, I say, slackers. Anyway, I now have a sane and powerful MUA :) combined with qmail maildrop and all is mostly well. As with any newbie, questions loom so bear with me. (Yes, I've poked around in the list archives; they've helped a couple of times already). 1) Firstly, does mutt support or will mutt ever support extended maildirs? I've never seen extended maildirs 'till I started using maildrop, but they're kinky. They allow for folders-within-folders which is very handy. 2) Replying and forwarding messages that have text/plain attachments (possibly others?) does not behave in a desirable manner. a) I do not want attachments of any sort to be part of a reply (whether text/plain or not). b) when forwarding, I'd like all attachments to be forwarded as just that: attachments. Not inline. 3) [this is a vim question; don't shoot me :)] I've seen mutts start up vim as their editor like vim -c ':0;/^$' which I understand puts the cursor on the first empty line. Any way to place it at the end of the file (eg, last line)? This is all for now. Thanks for any and all feedback. krjw
Re: a number of newbie questions
* krjw [EMAIL PROTECTED] [2002-08-29 11:57]: Greetings, mutts. Yo. 1) Firstly, does mutt support or will mutt ever support extended maildirs? I've never seen extended maildirs 'till I started using maildrop, but they're kinky. They allow for folders-within-folders which is very handy. I don't know, but have you tried it? It seems like it would work. 3) [this is a vim question; don't shoot me :)] I've seen mutts start up vim as their editor like vim -c ':0;/^$' which I understand puts the cursor on the first empty line. Any way to place it at the end of the file (eg, last line)? set editor=vim +$ works for me, although that feels not right. (darren) -- I'm astounded by people who want to 'know' the universe when it's hard enough to find your way around Chinatown. -- Woody Allen
Re: a number of newbie questions
+-- On 29082002 12:16:11 +, darren chamberlain uttered: | * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: | | 1) Firstly, does mutt support or will mutt ever support extended | maildirs? I've never seen extended maildirs 'till I started using | maildrop, but they're kinky. They allow for folders-within-folders | which is very handy. | | I don't know, but have you tried it? It seems like it would work. Ya. I have a test maildir FOO, with a 'folder' bar, and bar has yet another 'folder' called blah. The structure looks like this (as created with the maildirmake prog that comes with maildrop): FOO FOO/tmp FOO/new FOO/cur FOO/.bar FOO/.bar/tmp FOO/.bar/new FOO/.bar/cur FOO/.bar/maildirfolder FOO/.bar.blah FOO/.bar.blah/tmp FOO/.bar.blah/new FOO/.bar.blah/cur FOO/.bar.blah/maildirfolder (maildirfolder is a regular file.) mutt sees FOO but has zero knowledge of bar or blah AFAICT. Thanks for the vim tip. krjw. | | (darren)
Re: a number of newbie questions
krjw wrote: +-- On 29082002 12:16:11 +, darren chamberlain uttered: | * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: 1) Firstly, does mutt support or will mutt ever support extended maildirs? I've never seen extended maildirs 'till I started using maildrop, but they're kinky. They allow for folders-within-folders which is very handy. I don't know, but have you tried it? It seems like it would work. Ya. I have a test maildir FOO, with a 'folder' bar, and bar has yet another 'folder' called blah. The structure looks like this (as created with the maildirmake prog that comes with maildrop): FOO FOO/tmp FOO/new FOO/cur FOO/.bar FOO/.bar/tmp FOO/.bar/new FOO/.bar/cur FOO/.bar/maildirfolder FOO/.bar.blah FOO/.bar.blah/tmp FOO/.bar.blah/new FOO/.bar.blah/cur FOO/.bar.blah/maildirfolder (maildirfolder is a regular file.) mutt sees FOO but has zero knowledge of bar or blah AFAICT. What if you change folders to .bar or .bar.blah/ ? I'm pretty sure that should work fine. There are a few approaches to the (annoying, IMHO) maildir++ approach of courier. 1) there is a patch for maildir++ support in the archives. the author says it's a total hack, but it should work. 2) make symlinks from ~/Mail/ or whatever to the courier folders (it Mail/bar/blah is a link to ~/Maildir/.bar.blah/ (or do it the other way around). 3) Use mutt via IMAP (folders will be in INBOX.) 4) call them by their regular name, but set mask=^\\. so that you see them in the browser. -- Will Yardley input: william @ hq . newdream . net .
Re: a number of newbie questions
On 08/29/02 12:16 -0400, darren chamberlain wrote: 3) [this is a vim question; don't shoot me :)] I've seen mutts start up vim as their editor like vim -c ':0;/^$' which I understand puts the cursor on the first empty line. Any way to place it at the end of the file (eg, last line)? set editor=vim +$ works for me, although that feels not right. I start vim thusly: set editor =vim +/^$ +'set nobackup' -c 'normal o' -c startinsert This puts me at a new line below the first non blank line, in insert mode. If you like, simply change 'normal o' to 'normal i' to omit the additional blank line. I use the blank line to make it easier when I need to reformat the first paragraph. That way, the headers don't get mangled when I execute gqip. The use of 'set nobackup' above is obvious. Also, while we're talking editors, I use: set tmpdir=~/tmp to ensure privacy of my temp files. Otherwise, they get written to /tmp, which is world readable. And,welcome to Mutt, krjw :) John
Re: a number of newbie questions
+-- On 29082002 12:04:04 +, Will Yardley uttered: | krjw wrote: | +-- On 29082002 12:16:11 +, darren chamberlain uttered: | | * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: | | 1) Firstly, does mutt support or will mutt ever support extended | maildirs? I've never seen extended maildirs 'till I started using | maildrop, but they're kinky. They allow for | folders-within-folders | which is very handy. | | I don't know, but have you tried it? It seems like it would work. | | Ya. I have a test maildir FOO, with a 'folder' bar, and bar has yet | another 'folder' called blah. The structure looks like this (as | created | with the maildirmake prog that comes with maildrop): | | | What if you change folders to .bar or .bar.blah/ ? | I'm pretty sure that should work fine. I can get into FOO/ but when attempting to get into .bar or .bar.blah via the change-folder function, mutt declares it's not a mailbox. | | There are a few approaches to the (annoying, IMHO) maildir++ approach | of | courier. | I'll look into your suggestions. No big issue. More of a luxury than anything to be able to nest maildirs. Thanks again, krjw.
Re: a number of newbie questions
+-- On 29082002 16:54:29 +, John P Verel uttered: | | I start vim thusly: set editor =vim +/^$ +'set nobackup' -c 'normal | o' -c startinsert This puts me at a new line below the first non | blank line, in insert mode. If you like, simply change 'normal o' to | 'normal i' to omit the additional blank line. I use the blank line to | make it easier when I need to reformat the first paragraph. That way, | the headers don't get mangled when I execute gqip. The use of 'set | nobackup' above is obvious. Ah yes that works quite well. Now all that's left is to get vim to sanely re-format quoted text (where the quoting text is an arbitrary N quote levels deep).:) I saw a thread somewhere about fiddling with vim's 'comments' setting, combind with gqap, but have yet to make sense of it. | Also, while we're talking editors, I use: | | set tmpdir=~/tmp | | to ensure privacy of my temp files. Otherwise, they get written to | /tmp, which is world readable. Yes, a good idea indeed. Although vim is smart enough to honor the TMPDIR environment variable (which I have set to ~/tmp as well), and so I wasn't concerned about setting it via mutt. | And,welcome to Mutt, krjw :) Thanks. The 'k' is for Keith, although many people insist my name's Kevin. hrmph. OT: I see you're an optonline user. So what do you think of Jimmy Dolan? If you're a Yanks fan you probably hate his guts. Anyway check out fuckedcompany.com and you'll see that ol' Jimmy and Cablevision aren't doing so hot. Cheers, krjw. | John
Re: a number of newbie questions
krjw wrote: On 29082002 12:04:04 +, Will Yardley uttered: krjw wrote: On 29082002 12:16:11 +, darren chamberlain uttered: * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: 1) Firstly, does mutt support or will mutt ever support extended maildirs? I've never seen extended maildirs 'till I started using maildrop, but they're kinky. They allow for folders-within-folders which is very handy. I don't know, but have you tried it? It seems like it would work. Ya. I have a test maildir FOO, with a 'folder' bar, and bar has yet another 'folder' called blah. The structure looks like this (as created with the maildirmake prog that comes with maildrop): What if you change folders to .bar or .bar.blah/ ? I'm pretty sure that should work fine. I can get into FOO/ but when attempting to get into .bar or .bar.blah via the change-folder function, mutt declares it's not a mailbox. What if you set folder to FOO? ie: set spoolfile=~/FOO/ set folder=~/FOO/ However, i think 'baz' (in FOO/bar.baz/) will show up as FOO/bar.baz/ rather than as a subfolder of bar. Perhaps you'd rather use IMAP, although this probably has its own set of problems. -- Will Yardley input: william @ hq . newdream . net .
Re: a number of newbie questions
On Thu, Aug 29, 2002 at 02:00:30PM -0400, krjw wrote: +-- On 29082002 12:16:11 +, darren chamberlain uttered: | * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: | | 1) Firstly, does mutt support or will mutt ever support extended | maildirs? I've never seen extended maildirs 'till I started using | maildrop, but they're kinky. They allow for folders-within-folders | which is very handy. this works. as a matter of fact i use it. i think iirc it works as far back as version 1.3. i use 1.5 now. what do you have setup for your spoolfile, mbox, mbox_type, folder? do you have bar and bar.blah set up as mailboxes? FOO FOO/tmp FOO/new FOO/cur FOO/.bar FOO/.bar/tmp FOO/.bar/new FOO/.bar/cur FOO/.bar/maildirfolder FOO/.bar.blah FOO/.bar.blah/tmp FOO/.bar.blah/new FOO/.bar.blah/cur FOO/.bar.blah/maildirfolder what happens if you use c and then type an absolute path to .bar or .bar.blah? a la /path/to/FOO/.bar (maildirfolder is a regular file.) perhaps the existance of this file is what is throwing mutt off. have you tried removing it? what is it there for? mutt sees FOO but has zero knowledge of bar or blah AFAICT. what do you mean, exactly? you can tell mutt that these are mailboxes by using the mailboxes command in your muttrc. a la mailboxes = /path/to/FOO mailboxes = /path/to/FOO/.bar mailboxes = /path/to/FOO/.bar.blah if you do this, you can use c and if there is new email in any of them mutt will automagically give it as the next choice. hth -- Peter Abplanalp Email: [EMAIL PROTECTED] PGP: pgp.mit.edu msg30519/pgp0.pgp Description: PGP signature
Re: a number of newbie questions
Doh again. Geeze this is two doh's in one day. Yes you are correct. It does work. I didn't realize that mutt had to be told explicitly about each of the sub-maildirs. *sigh* is it friday yet? Thanks again. krjw. +-- On 29082002 16:20:55 +, Peter T. Abplanalp uttered: | On Thu, Aug 29, 2002 at 02:00:30PM -0400, krjw wrote: | +-- On 29082002 12:16:11 +, darren chamberlain uttered: | | * krjw [EMAIL PROTECTED] [2002-08-29 11:57]: | | | | 1) Firstly, does mutt support or will mutt ever support extended | | maildirs? I've never seen extended maildirs 'till I started using | | maildrop, but they're kinky. They allow for folders-within-folders | | which is very handy. | | this works. as a matter of fact i use it. i think iirc it works as | far back as version 1.3. i use 1.5 now. | | what do you have setup for your spoolfile, mbox, mbox_type, folder? | do you have bar and bar.blah set up as mailboxes? | | FOO | FOO/tmp | FOO/new | FOO/cur | FOO/.bar | FOO/.bar/tmp | FOO/.bar/new | FOO/.bar/cur | FOO/.bar/maildirfolder | FOO/.bar.blah | FOO/.bar.blah/tmp | FOO/.bar.blah/new | FOO/.bar.blah/cur | FOO/.bar.blah/maildirfolder | | what happens if you use c and then type an absolute path to .bar or | .bar.blah? a la /path/to/FOO/.bar | | (maildirfolder is a regular file.) | | perhaps the existance of this file is what is throwing mutt off. have | you tried removing it? what is it there for? | | mutt sees FOO but has zero knowledge of bar or blah AFAICT. | | what do you mean, exactly? you can tell mutt that these are mailboxes | by using the mailboxes command in your muttrc. a la | | mailboxes = /path/to/FOO | mailboxes = /path/to/FOO/.bar | mailboxes = /path/to/FOO/.bar.blah | | if you do this, you can use c and if there is new email in any of them | mutt will automagically give it as the next choice. | | hth | | -- | Peter Abplanalp | | Email: [EMAIL PROTECTED] | PGP: pgp.mit.edu
