":source ~/.muttrc" command weirdly moves message around in index

2008-06-14 Thread Russell Hoover
Suddenly I've discovered that when I try to re-load my .muttrc with the ":source ~/.muttrc" command, the last message in my index (number 920), is re-positioned as number 576. Other messages are also moved around. If I change folders out of the inbox and then back into it, the message-order is res

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, June 15 at 01:04 AM, quoth Russell Hoover: > Suddenly I've discovered that when I try to re-load my .muttrc with the > ":source ~/.muttrc" command, the last message in my index (number 920), is > re-positioned as number 576. Other messages

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Russell Hoover
On Sun 06/15/08 at 10:39 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > Probably a folder-hook that sets your sorting order whenever you enter > the INBOX. Well, I have what's below, but I've these forever: folder-hook . set sort=threads folder-hook .'set index_f

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, June 15 at 02:45 PM, quoth Russell Hoover: >On Sun 06/15/08 at 10:39 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > >> Probably a folder-hook that sets your sorting order whenever you enter >> the INBOX. > >Well, I have what's below, bu

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Russell Hoover
On Sun 06/15/08 at 02:50 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > Think of it this way: > mutt reads your muttrc (sort=date) > mutt opens your inbox (hook triggered, sort=threads) > you tell mutt to re-read the muttrc (sort=date) > you tell mutt to re-open your inbox

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, June 15 at 08:11 PM, quoth Russell Hoover: >On Sun 06/15/08 at 02:50 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: >> Think of it this way: >> mutt reads your muttrc (sort=date) >> mutt opens your inbox (hook triggered, sort=th

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Russell Hoover
On Sun 06/15/08 at 07:22 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: [that I wrote] > >folder-hook <|sent|cv|dm|fabio'set index_format= etc > > ^^^ > > . . . duplication of sent-folder names. > Well, not necessarily. Remember, you're providing a *pattern*, so that

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, June 15 at 09:54 PM, quoth Russell Hoover: >I mean, what I need is surely this: > > folder-hook <|cv|dm'set index_format="whatever" Yes, that is more succinct, assuming that the only reason "sent" was in there was to match ag

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Russell Hoover
On Sun 06/15/08 at 09:40 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > [...] that "sent" string in the original pattern will also match folders > named "abSENT" and "SENTimental" and "esSENTial". So it was entirely > possible that the "sent" string was not redundant, and was actually > inten

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Russell Hoover
On Sun 06/15/08 at 11:15 PM -0400, Russell Hoover <[EMAIL PROTECTED]> wrote: > Absolutely. Though I'm partial to the plus-sign, so I used that > instead of "=". > folder-hook '(<|+cv|+dm)$''set index_format="whatever"' ^ ^ Looks like I'm better off with the equal-sig

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, June 15 at 11:29 PM, quoth Russell Hoover: >On Sun 06/15/08 at 11:15 PM -0400, Russell Hoover <[EMAIL PROTECTED]> wrote: > >> Absolutely. Though I'm partial to the plus-sign, so I used that >> instead of "=". > >> folder-hook '(<|+cv|+dm)

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-16 Thread Russell Hoover
On Sun 06/15/08 at 09:40 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > [...] that you use something more like this: > folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"' The only problem I'm having with this: '(<|=cv|=dm)$' instead of this: '<|cv|dm' in this:

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-16 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, June 16 at 03:15 PM, quoth Russell Hoover: >On Sun 06/15/08 at 09:40 PM -0500, >Kyle Wheeler <[EMAIL PROTECTED]> wrote: > >> [...] that you use something more like this: >> folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"' > > >T

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-16 Thread Christian Brabandt
Hi Russell! On Mon, 16 Jun 2008, Russell Hoover wrote: > How can I keep the form you've suggested and also get the results of > %c instead of %3l ? Have you tried something like the following format: (%?l?%4l&%4c?) This will display the line number if available otherwise it will print the byt

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-16 Thread Russell Hoover
On Mon 06/16/08 at 02:30 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > Hmmm... so it's not matching? Interesting. Try deconstructing it, to > see what's breaking the match. For example, remove the $ off the end, > and see if that helps. I originally had this: <|cv|dm and you sugge

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-16 Thread Russell Hoover
On Mon 06/16/08 at 09:38 PM +0200, Christian Brabandt <[EMAIL PROTECTED]> wrote: > Have you tried something like the following format: (%?l?%4l&%4c?) > This will display the line number if available otherwise it will print > the byte size. This is perfect. It's amazing how mutt has a solution f

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-17 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover: > I originally had this: > ><|cv|dm > > and you suggested this: > >'(<|=cv|=dm)$' > > but the only two things that works are these: > ><|cv|dm and '<|cv|

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-17 Thread Rocco Rutte
Hi, * Kyle Wheeler wrote: On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover: I originally had this: <|cv|dm and you suggested this: '(<|=cv|=dm)$' but the only two things that works are these: <|cv|dm and '<|cv|dm' No other combinat

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-19 Thread Russell Hoover
On Tue 06/17/08 at 02:30 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > Use whatever works for you; I just recommend using a tighter pattern > when possible. Your original pattern of just two lowercase letters > seems to be just begging to match things you don't intend. I've never actually

Re: ":source ~/.muttrc" command weirdly moves message around in

2008-06-20 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, June 20 at 01:19 AM, quoth Russell Hoover: > I've never actually once ever had any matching I didn't want on > > <|cv|dm > > in the line > > folder-hook '<|cv|dm''set index_format="%3C %Z %[%m/%d] %-22.22F \ > %?l?%4l&%4c?