Re: Regex - Date Range
* Hardy Merrill [EMAIL PROTECTED] [000822 14:42]: so since I want to tag everything with a "sent" date less than Jul 7, I entered "shift-T", and it asks me to enter the pattern to tag, so I enter ~d [5 Jul 2000] but that doesn't work. What format does the date that I enter have to be in? Try "~d -5/7/2000" to tag all messages older that July 5th, 2000. -- christian molls student of laws univ of cologne
Re: Again: gpg and screen refresh
* Henrique M. Holschuh [EMAIL PROTECTED] [000819 18:51]: Strange, it works fine in 1.2.x, all the gpg: messages just get tacked in the PGP output block (for signed but NOT encripted messages). Is the problem you're having only triggered by signed AND encripted messages? (and signed AND encripted by mutt or by standalone GPG?) It happens with both signed and signed+encrypted messages. However, I think I can live with the "2/dev/null" solution. Christian
Re: Strategies for archiving mails
* Kai Weber [EMAIL PROTECTED] [000820 19:13]: I am searching for some tips how to archive and collect my mails. I do not want to delete mails I get. After 3 months using Linux my mailboxes grow and grow. How do you sort and archive your mails? I want to collect some possible solutions for first information and to see what is possible. If it is a integrated mutt-procmail-solution it would be nice. There has been an interesting thread on this topic starting end of July. The subject was "automatic mail archiving". David Champion posted a nice solution to the problem on July 31 (not exactly sure about that date). It spoils make, procmail, and mutt and a clever use of symbolic links. I have it running here for about ten mailing lists, and it works beautifully. -- christian molls student of laws univ of cologne
Re: New mutt user
* Dave Kufta [EMAIL PROTECTED] [000820 19:51]: pgp-6.5.1I . I noticed in some screenshots a very nice interface for mutt in xwindow enviroment which had very nice color and a menu bar at the top which included a button for pgp among others. Could someone on the list possibly suggest where I may find a muttrc file that would allow these features. I found the screenshot I'm referring to at the main web site for mutt but don't see in any of the muttrc files that are there a way to enable the menu bar. If you take another, closer look at the text accompanying the screenshots, you will read that the menu bar does not belong to mutt, but is a feature of the terminal application mutt runs in (in this screenshot it's ETerm, rxvt can do it too, maybe other). -- christian molls student of laws univ of cologne
Re: Install v. Patches
* George Wright [EMAIL PROTECTED] [000816 14:22]: I want to upgrade from 1.0.1i to the current 1.2.5i. What is the best approach for this - installing patches in successive order or just downloading the current tarball and installing it? I guess it is a matter of taste and bandwidth. If you sit at home with a 14.4 modem connection and still want to live at the bleeding edge of mutt development, downloading the small patches will save you time and money. If you have got a T3 link to the net, and 2 or 3 MB more or less are a matter of seconds, just get the tar ball and save yourself the work of fiddling with patches. Christian
Re: Folder overview ?
* Daniel Kollar [EMAIL PROTECTED] [000816 16:58]: I'm missing an incoming folders overview. Procmail is spooling the incoming mail to different folders. How do I detect, which folders content new mail without entering each? Put something like the following into your muttrc: mailboxes ! =linux-users =mutt-users ... Pressing "c" change-folder and "?" will show a mailbox overview, where folders containing new messages have a "N" in front of their name. BTW, mutt has a pretty good manual...
Re: Loading mail setup at editor (vim) start
* Johannes Zellner [EMAIL PROTECTED] [000731 11:50]: how can I let read some special mail configs (e.g. set tw=72) when edit a email/news messages? autocmd FileType mail set tw=72 nocin ai expandtab (this is what I have) au BufNewFile,BufRead /tmp/mutt* source ~/.vim/mutt_vimrc (this is what I have) The advantage of this solution is that it also works on messages which have been postponed and are recalled (via the "R" command). My vim 5.4 fails to properly detect the syntax in those cases, and Johannes' autocmd would not be executed. Which leads to the question: why does syntax detection work on all mails except that have been postponed and are recalled? -- christian molls student of laws univ of cologne
