Re: replying to unwrapped messages with vi
- On Tue, 01.Oct.2002, 09:12EDT, Ken Weingold uttered: On Tue, Oct 1, 2002, Elimar Riesebieter wrote: I use gqap in vim. Thats for leaving the qotes at start of line. Oh, yeah. Q} will preserve quotes too, but I forgot that I have Q remapped to gq, since I had gotten used to the Q in vim 4 I think. Or something like that. :) gqap in conjunction with 'comments' works well. But I'm curious: how do folks handle reformatting text with multiple levels of quoting? Ciao, Keith.
Re: download pgpwrap from where?
- On Thu, 26.Sep.2002, 13:15EDT, savanna uttered: Where do I download pgpewrap from? It's referred to in the sample muttrc files, for encrypting mail with gpg, however I can't find it anywhere on the web (though I've found hundreds of references to using it in my .muttrc ;-) ). One place it lives is in the mutt-1.4i source distribution. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
Re: mutt crashes -- 1.2.5 - 1.4
- On Fri, 20.Sep.2002, 11:42EDT, MindFuq uttered: How do I upgrade mutt? I tried using rpm with the upgrade option, and it had a dependancy on libc.so.6(GLIBC_2.2). Then when I tried to upgrade GLIBC, I got several screenfulls of other programs that require the old version that I'm using. I got the feeling I would have scrap everything and install the latest OS. No need to scrap everything. Just go grab the source tarball and build it yourself. Or better yet you could use a spec file and build your own mutt RPM which you could then install. Doesn't look like the 1.4i source tarball comes with a spec so you'd have to find on on the net somewhere or write it yourself. If I go get the latest tarball, will that have the dependancy issue I ran into with the rpm file? Not if you build mutt from source. Ciao, Keith. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
mailbox was externally modified
I use =sent-mail as $record. When mutt is in =sent-mail and I forward a message that is in =sent-mail, mutt claims Mailbox was externally modified. Flags may be wrong. ``Externally''? Um, ok. The only thing talking to =sent-mail is mutt itself. What gives? Cheers, Keith. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
%L, %l in $status_format
Greetings. With no limit set, I would expect %L in $status_format to expand to either 0K (that's zero-K, not okay) or the full size of the mailbox (I do not know which of these behaviors is intended). Apparently it expands to both (finish reading before you remark please). When intially in a mailbox, implicitly with no limit set, %L == 0K. If the user sets the limit to ``.'' (translation: explicitly unsets the limit pattern, even though there already is none), %L then expands to the full mailbox size. It seems that %L doesn't know what it should do when there is no limit pattern. This a minor inconsistancy worked around by either %?L?%L%l? or %?L?%L0? depending on whether or not %L should be zero when there is no limit pattern. Inconsistent with what? %M. %M _always_ expands to the number of messages shown, regardless of whether there is a limit pattern or not. Using the string %M/%L in $status_format in a mailbox with 100 messages yields 100/0K. Ciao. Keith. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
local date
Greets. Is there any intuitive way to get the ``Date:'' header (as shown in the pager) to always show the time converted to my local time zone, or GMT, or any given time zone so long as it's consistent across all messages? Thanks, Keith
Re: local date
- On Tue, 10.Sep.2002, 13:58EDT, Mark J. Reed uttered:
On Tue, Sep 10, 2002 at 01:48:19PM -0400, Mark J. Reed wrote:
Simply replace %d with %D in the value of the $index_format
Whups, I lied. I mean, that would be correct if you were using
%d *outside* of %{...}, but stuff inside %{...} is strftime(3) format
characters, not mutt format characters. To use local time
instead of sender's time with the same strftime format,
just change the {} to []:
set index_format=%4C%Z%[%b %d] %-15.15L (%4l)%s
Ah yes this works well for the index itself. Thanks! However it would
be useful to do the same conversion-to-local-TZ for the 'Date:' header
in the pager. Any ideas?
Regards,
Keith
Re: local date
- On Tue, 10.Sep.2002, 15:05EDT, Gary Johnson uttered: On Tue, Sep 10, 2002 at 01:58:54PM -0400, Mark J. Reed wrote: On Tue, Sep 10, 2002 at 01:48:19PM -0400, Mark J. Reed wrote: set index_format=%4C%Z%[%b %d] %-15.15L (%4l)%s To see the local time as well as the date in the pager, you might also want to set 'pager_format'. This is what I use: set pager_format=%4C %Z %[!%b %e at %I:%M %p] %.20n %s # This format is arranged more # like the index_format and # includes the local time at # which the message was sent. # Default: -%Z- %C/%m: %-20.20n %s HTH, Gary D'oh! That's the trick. Thanks a bunch to you and Mark for the quick feedback. I'll RTFM... again. :) -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
Re: mutt + procmail + qmail
- On Tue, 10.Sep.2002, 22:00EDT, Keith R. John Warno uttered: (Every dir below ~/Mail is assumed to be in maildir format; this picks up things like sent-mail and postponed and other fcc locations, so mutt winds up claiming things like 'new mail in =sent-mail' after sending a mail out, but this is OK for me.) Hrmm well actually not for =sent-mail, which is a good thing. But it does alert about 'new mail' in =postponed which is not a bad thing either. :) Ciao, Keith. -- Isn't it time we care and lose the hate Understand our fears -- Dream Theater, Blind Faith
Re: mutt + procmail + qmail
- On Tue, 10.Sep.2002, 19:58EDT, Michael P. Soulier uttered: On 11/09/02 Johan Almqvist did speaketh: # cat ~/.qmail |preline procmail -t ~/.procmailrc # cat ~/.procmailrc DEFAULT=~/Maildir/ #cat ~/.muttrc mailboxes ~/Maildir/ I take it that your other mail folders then would be sub-folders of ~/Maildir? My sysadmin recently told me that was a bad idea. [snip] Smack your sysadmin. Maildir format, that is 'extended maildir' format, happily allows for nested maildirs. You wind up with structure that looks like: foo/ foo/cur/ foo/new/ foo/tmp/ foo/.bar/ foo/.bar/cur/ foo/.bar/new/ foo/.bar/tmp/ .bar is obviously a 'sub-folder' of foo; extended-maildir-aware mail clients should strip the dot and just show it to you as 'bar'. mutt, from what I've seen, doesn't do this. It shows you verbatim: foo/.bar/, which is fine for me. :) I don't use procmail but rather maildrop which knows about maildirs (extended), along with qmail. My ~/.qmail: $ cat .qmail # simple one-liner |maildrop I've got maildrop delivering to ~/Mail/INBOX/ by default (ie, when no other rule is satisfied). List mail winds up in a structure like: ~/Mail/lists/.mutt/ ~/Mail/lists/.kernel/ ...etc Note that ~/Mail/lists/ is itself a maildir (although I don't use it for receiving mail currently). The ~/.mutt/muttrc contains: set folder=~/Mail set mbox_type=Maildir set spoolfile=~/Mail/INBOX mailboxes `mdirs` `mdirs` is a simple shell script to find all the maildirs: #!/bin/bash # exec find ~/Mail -type d -mindepth 1 \ \( -name tmp -o -name cur -o -name new \ -prune \) \ -o \ \( -type d -mindepth 1 -printf '%p ' \) (Every dir below ~/Mail is assumed to be in maildir format; this picks up things like sent-mail and postponed and other fcc locations, so mutt winds up claiming things like 'new mail in =sent-mail' after sending a mail out, but this is OK for me.) Anyway, good luck! Sorry I don't have any procmail recipes. :/ Regards, Keith.
%s expansion in query_command
Regarding mutt 1.4i: Is the %s which the query_command variable expects expanded by mutt in the same manner as %s in mailcap entries? I.e., Keep the %-expandos away from shell quoting... Mutt does this for you (as described in the mailcap sections)? The explanation of query_command gives an example (manual.txt:2209) that uses single-quotes around the %s. The example doesn't work right when the query contains shell metacharacters (eg, *); the metachars get expanded by the shell. Without the quotes it seems to work correctly. Rather misleading; I welcome any useful clarification of this. Thanks. Ciao, Keith.
