Re: vvv.nntp and local spools
On Sun, Feb 17, 2002 at 10:27:40PM -0600, Peter Horst wrote: Can the vvv.nntp package be used with a local spool, ? la slrn/slrnpull? I just patched 1.3.25i with it, and it's great, but it would be better without the slow Internet article checking, etc. You're farther along them me. This is the first time I've needed to use the patch program. I think, for vvv.nntp, I must turn the top of the textfile into a little script, then patch, then ./configure, then make, and make install. But I don't know the flags to use with patch, or where I should run the patch, with respect to the mutt directory I want to modify. -- William GUynes
Toggle to weed=yes for fwding only
Has anyone else had a desire to be able to toggle weed=yes for only certain instances of pager, reply, or forward? I tend to not want to see all headers normally (having a full screen of headers just doesn't entice me to read the message). But, I tend to need them when I report spam using forward. I've given thought to re-binding the default forward key to... 1) set weed=yes 2) forward-message 3) set weed=no From looking at all the available examples, I think I'll have to make a macro then bind the f key to it. Is there a way to perform a set command in a keybinding? If so, what's the syntax for multiples, assuming no macro? Also, I'm not sure I can perform the toggle while in index mode, but would have a better chance in pager mode. Can the binding even do the toggle in index menu? My manual testing using default h key always opens the message by default, but appears to perform the toggle. -- William Guynes
Re: Toggle to weed=yes for fwding only
On Fri, Feb 08, 2002 at 09:35:56PM -0600, Jeremy Blosser wrote: [snip!] If you turn off $forward_decode you'll get this effect without touching $weed. I looked into that, but it has other side effects with MIME messages. I've given thought to re-binding the default forward key to... 1) set weed=yes 2) forward-message 3) set weed=no Er, you do realize this turns $weed on for forwarding, and off otherwise, which is the opposite of what you first said you wanted? [snip!] Whups. Yeah, that's back'erds. A keybinding is to bind a key to a defined function in a key map. Anything more complex is by definition a macro. There's nothing bad about using a macro instead of keybinding, either, so it doesn't really matter... [snip!] Ah. Great info. I was struggling with the concept of the differences between the two. This clears it up perfectly. Longer answer: Macros can call enter-command from anywhere, and 'set' is always a valid command. Wonderful. Will's example (the other Will, not me) works with the header parameter, but the syntax was more than enough for me to figure it out. You know what's disgusting? This is the most configurable client I've ever had to deal with, and I love it. But I'm spending way too much time tweaking it. I need to get out more. *sigh* -- William Guynes
Index colors
Is it possible to color the message index lines according to message status? I see where a pattern can be used, and some testing show the author or subject as valid pattern matches, maybe a way to adjust the pattern to read the status tag? -- William Guynes
Re: Index colors
On Mon, Feb 04, 2002 at 03:34:39PM -0500, Mike Schiraldi wrote: [snip!] I presume you've already read through http://mutt.org/doc/manual/manual-4.html#patterns Ack! The definition of patterns has just taken on a whole new meaning. Yeah, this is what I meant. -- William Guynes
Getting start with Mutt and IMAP
I'm trying to get moved over to mutt. I've had it with Pine roles,
it's driving me nuts.
IMAP implementation has me a bit confused. I have 3 IMAP mailboxes,
on 3 diferent servers. If I understand the docs correctly, I can
switch between them using the 'c' command inside Mutt. Typing out
the imap://servername/INBOX isn't working though.
The documentation talks about commands available. They don't
appear to work in the Muttrc file. (Assume, for simplicity, it's a
single user system and I'm making configs in the master Muttrc file)
I've tried both mailboxes and account-hook. The only thing that
worked was spoolfile in {server}INBOX format, but not in
imap://server/INBOX format. However, that assumes only one IMAP
box.
Can someone straighten me out here? The documentation talks about
initialization files. These are somehow different than RC files?
The Mutt and IMAP document tends to gloss over these details.
E.g.
1.1 To point mutt to an IMAP mailbox, write your mailbox in IMAP
URL format:
imap://hostname/mailbox
Write it? Write it where? :) rc file? (didn't work, maybe was
using wrong parameter) initialization file? commandline? (didn't
work with -f)
I'm just missing some mental building blocks that the docs don't
cover.
--
William Guynes
