tag pattern

[bill lam]

Hi all,
I often need to tag the same pattern. Instead of typing each time, how
can I save the following and bind it shortcut key?
tag pattern
 T\[.*patch.*\]   

TIA
-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

Re: tag pattern

[Rejo Zenger]

++ 02/10/08 21:45 +0800 - bill lam:
>I often need to tag the same pattern. Instead of typing each time, how
>can I save the following and bind it shortcut key?
>tag pattern
> T\[.*patch.*\]   

You would need to use a "macro". Untested:

  macro  pager,index  \ca  "T\[.*patch.*\]"   # tag using pattern

See:

 - http://www.mutt.org/doc/manual/manual-3.html#ss3.6
 - http://wiki.mutt.org/?MuttGuide/Macros
 



-- 
Rejo Zenger . <[EMAIL PROTECTED]> . 0x75FC50F3 . 
GPG encrypted e-mail prefered. 


signature.asc
Description: Digital signature

Re: tag pattern

[bill lam]

On Thu, 02 Oct 2008, Rejo Zenger wrote:

> ++ 02/10/08 21:45 +0800 - bill lam:
> >I often need to tag the same pattern. Instead of typing each time, how
> >can I save the following and bind it shortcut key?
> >tag pattern
> > T\[.*patch.*\]   
> 
> You would need to use a "macro". Untested:
> 
>   macro  pager,index  \ca  "T\[.*patch.*\]"   # tag using pattern

Thank you Rejo! I tried that \ inside quotes should be escaped too.

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

tag-prefix

[bill lam]

Suppose I tag 2 msg inside a thread and then collapse it so that those
tag items are invisible. Then tag-prefix (eg ;d) can not operate on
those item. Apparently tag-prefix only applies to visible items, is
this intended and what is the workaround?

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

Re: tag-prefix

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday, October  2 at 11:21 PM, quoth bill lam:
> Suppose I tag 2 msg inside a thread and then collapse it so that those 
> tag items are invisible. Then tag-prefix (eg ;d) can not operate on 
> those item. Apparently tag-prefix only applies to visible items, is 
> this intended and what is the workaround?

My understanding (and I may be wrong) is that this is intentional. The 
reasoning stems from the "limit" functionality, and is essentially: 
users shouldn't be surprised that something got deleted. Deleting 
things you can't see makes unfortunate, uncorrectable mistakes a very 
real probability. Imagine, for example, that you'd tagged something, 
forgotten about it, and then limited your view, tagged a few things 
and then told mutt to delete all tagged messages. Should the invisible  
tagged message be deleted? There may be a difference of opinion, but 
in the interest of not surprising the user, "no" is perfectly valid. 
And as an alternate behavior to prompting me every time with "do you 
really want to delete this message?" (which would be *really* 
annoying), I think it makes a lot of sense.

Now, whether this argument still ought to apply in the case of 
collapsed threads, I don't know, and that's something worth discussing 
from an interface point of view.

~Kyle
- -- 
This country, with its institutions, belongs to the people who inhabit 
it. Whenever they shall grow weary of the existing government, they 
can exercise their constitutional right of amending it, or exercise 
their revolutionary right to overthrow it.
 -- Abraham Lincoln
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkjk6V8ACgkQBkIOoMqOI14GSgCg4UnXdVjDDQtzZThVuDoW+bGl
fdMAnjJ+ufnpkaqhO/HOB9vnU3v084Sz
=FlW5
-END PGP SIGNATURE-

Re: tag-prefix

[bill lam]

On Thu, 02 Oct 2008, Kyle Wheeler wrote:

> On Thursday, October  2 at 11:21 PM, quoth bill lam:
> > Suppose I tag 2 msg inside a thread and then collapse it so that those 
> > tag items are invisible. Then tag-prefix (eg ;d) can not operate on 
> > those item. Apparently tag-prefix only applies to visible items, is 
> > this intended and what is the workaround?
> 
> My understanding (and I may be wrong) is that this is intentional. The 
> reasoning stems from the "limit" functionality, and is essentially: 
> users shouldn't be surprised that something got deleted. Deleting 
> things you can't see makes unfortunate, uncorrectable mistakes a very 
> real probability. Imagine, for example, that you'd tagged something, 
> forgotten about it, and then limited your view, tagged a few things 
> and then told mutt to delete all tagged messages. Should the invisible  
> tagged message be deleted? There may be a difference of opinion, but 
> in the interest of not surprising the user, "no" is perfectly valid. 
> And as an alternate behavior to prompting me every time with "do you 
> really want to delete this message?" (which would be *really* 
> annoying), I think it makes a lot of sense.
> 
> Now, whether this argument still ought to apply in the case of 
> collapsed threads, I don't know, and that's something worth discussing 
> from an interface point of view.

I can agree to your argument, either way half of innocent users will be
surprised. Can I make a ;! or ;; that will apply to all tagged items,
visible or not?

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

Re: tag-prefix

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Friday, October  3 at 12:04 AM, quoth bill lam:
> I can agree to your argument, either way half of innocent users will 
> be surprised. Can I make a ;! or ;; that will apply to all tagged 
> items, visible or not?

Not that I'm aware of. The only workaround I know is to make 
everything visible (e.g. liberal use of the  toggle).

~Kyle
- -- 
Necessity is the plea for every infringement of human liberty; it is 
the argument of tyrants; it is the creed of slaves.
-- William Pitt
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkjk98gACgkQBkIOoMqOI16NfACgl6+qKhDsvsXHp9Wrp+d45s5e
P68An1xWYJJ66oD6ZyxuPCR8cI9zdqBT
=Voxb
-END PGP SIGNATURE-

Re: tag-prefix

[Christian Ebert]

* bill lam on Friday, October 03, 2008 at 00:04:46 +0800
> Can I make a ;! or ;; that will apply to all tagged items,
> visible or not?

A tiny bit more longwinded, but you could first limit to ~T (this
works regardless of whats visible) and then tag-prefix.

c
-- 
\black\trash movie_C O W B O Y_  _C A N O E_  _C O M A_

Welturaufführung -->> http://www.blacktrash.org/underdogma/ccc.html
World première   -->> http://www.blacktrash.org/underdogma/ccc-en.html

Re: mutt tmp files

[Wolf Wiegand]

Hi,

Kyle Wheeler wrote:

> On Wednesday, October  1 at 09:13 AM, quoth [EMAIL PROTECTED]:
> > Hmm.  Mutt has *always* left plenty of files behind for me.  
> > Starting with 1.4.something and all the way into 1.5.18.  On OSX 
> > Panther, Tiger, and Leopard.  It leaves things in the folder I 
> > defined as the tmpdir.  Usually the files are empty, but sometimes 
> > they are saved states of mails I was writing.
> >
> > These files always have a name that looks something like:
> >
> > mutt-hostname-501-somenumbers-somemorenumbers
> >
> > I manually clean them out once in a while.  I thought this was 
> > normal.  Is mutt bugging out on the Mac?
> 
> Files of that name pattern are from composing a message, and *should* 
> be deleted when the message is sent.

I've encountered the same thing here and just rechecked. With mutt
running, reading this mailing list, I find these files under /tmp:

 3870 Oct  2 22:34 mutt-denkbrett-1000-16736-253
 4511 Oct  2 22:34 mutt-denkbrett-1000-16736-259
 4842 Oct  2 22:35 mutt-denkbrett-1000-16736-261

(denkbrett == hostname, 1000==uid, 16736 seems to bei mutt's pid)
I wrote some mails in the same mutt session before.

After exiting mutt, all files are gone. Restart mutt, open this list's
mailing list folder, and read some mails, these files reappear:

 1079 Oct  2 22:36 mutt-denkbrett-1000-21269-14
 1648 Oct  2 22:44 mutt-denkbrett-1000-21269-16
 5662 Oct  2 22:36 mutt-denkbrett-1000-21269-3
 4237 Oct  2 22:36 mutt-denkbrett-1000-21269-7
 4849 Oct  2 22:36 mutt-denkbrett-1000-21269-9

One file contains the mail I am composing right now, the other files
contain various answers from this thread.

If I switch to another imap folder, these files are deleted.

I am using mutt 1.5.13 (or rather the heavily patched version) from
Debian unstable.


Cheers,

Wolf

-- 

Re: mutt tmp files

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday, October  2 at 10:48 PM, quoth Wolf Wiegand:
> After exiting mutt, all files are gone. Restart mutt, open this 
> list's mailing list folder, and read some mails, these files 
> reappear:

Interesting... I wonder... I'm guessing that you don't use mutt's 
mcache setting? I bet if you did, those files wouldn't exist (they'd 
be stored in the mcache location instead).

~Kyle
- -- 
Eskimo: If I did not know about God and sin, would I go to hell?
Priest: No, not if you did not know.
Eskimo: Then why did you tell me?
   -- Annie Dillard
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkjlNP8ACgkQBkIOoMqOI17f3ACg3AOHiyjGvN7wXRdBgYI53A+2
+IEAn2nsS/VGK4sIDjGM/ElQdkIvzniU
=qZoP
-END PGP SIGNATURE-

Mutt, multiple accounts problems

[Kabel]

Hello,

I'm not so new to mutt, and i really like it.
I'm trying to make it work with multiple imaps & pop3 accounts, but I get a 
lot of problems. So I would be pleased if someone could give me a tip. Even 
after finding some example I didn't managed to make it work :S

I'm completely lost now, I tried to make it work the whole day, and failed 
miserably.
So my last hope is this mailing list.
Does somebody could show me his .muttrc where he's accessing more than one 
mail server? I would be very happy for this help.

Greetings,

Kabel

Re: Mutt, multiple accounts problems

[Russell L. Harris]

* Kabel <[EMAIL PROTECTED]> [081002 16:07]:
> Hello,
> 
> I'm not so new to mutt, and i really like it.
> I'm trying to make it work with multiple imaps & pop3 accounts, but I get a 
> lot of problems. So I would be pleased if someone could give me a tip. Even 
> after finding some example I didn't managed to make it work :S
> 
> I'm completely lost now, I tried to make it work the whole day, and failed 
> miserably.
> So my last hope is this mailing list.
> Does somebody could show me his .muttrc where he's accessing more than one 
> mail server? I would be very happy for this help.
> 
> Greetings,
> 
> Kabel

Rather than trying to do everything with mutt, why not take advantage
of well-designed and easy to maintain special-purpose software?

For example, use getmail4 to fetch your mail, and maildrop to sort
messages.

RLH