Re: [SPAM?] Re: no MUTTRC environment variable?
On Sun, Jul 3, 2016 at 12:43 AM, Jon LaBadiewrote: >> > On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote: >> >> >> >> I have read the environment variables section in 'man mutt' and there >> >> does not seem to be a MUTTRC environment variable. One can set using >> >> -F option but sometime environment variable is nice. >> >> >> >> Can someone confirm this is correct? Is there a reason for this? >> > > > How about implementing your own with a mutt alias? > > > alias mutt='mutt ${MUTTRC:+-F ${MUTTRC}}' > > If MUTTRC is not set, or is the empty string, this becomes > just "mutt" and ~/.muttrc will be used as normal. But if > MUTTRC is set it becomes "mutt -F ${MUTTRC}" and uses the > rc file specified in the variable. > > Jon > -- > Jon H. LaBadie j...@jgcomp.com > 11226 South Shore Rd. (703) 787-0688 (H) > Reston, VA 20190 (703) 935-6720 (C) Interesting idea, Jon! I will consider this for my personal setup. Kind regards, Xu
Re: Delete all threads which are incomplete?
On Sat, Jul 02, 2016 at 10:27:27PM +0200, Matthias Beyer wrote: > On 02-07-2016 21:59:22, Francesco Ariis wrote: > > On Sat, Jul 02, 2016 at 06:23:38PM +0200, Matthias Beyer wrote: > > > This is awesome! I removed the "~l~N" part as well as "" for my > > > setup. The former so I can apply it everywhere and the latter so I can > > > see what I did to make this work and learn from it. > > > > Dabbling with mutt during half-time, I see ;) > > Glad it was of help! > > half-time? What do you mean? Oh, mutt mailing list decided to deliver the message half-time during Euro 2016 match - Italy vs. Germany, I notice now the actual timestamp is `06:23:38PM +0200`. I found it amusing enough since the domain I am using to write this is .it, while yours is .de :P In case you actually watched and/or care about it: good game! Long live mutt -F
Re: [SPAM?] Re: no MUTTRC environment variable?
> > On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote: > >> > >> I have read the environment variables section in 'man mutt' and there > >> does not seem to be a MUTTRC environment variable. One can set using > >> -F option but sometime environment variable is nice. > >> > >> Can someone confirm this is correct? Is there a reason for this? > > How about implementing your own with a mutt alias? alias mutt='mutt ${MUTTRC:+-F ${MUTTRC}}' If MUTTRC is not set, or is the empty string, this becomes just "mutt" and ~/.muttrc will be used as normal. But if MUTTRC is set it becomes "mutt -F ${MUTTRC}" and uses the rc file specified in the variable. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
[SPAM?] Re: [SPAM?] Re: no MUTTRC environment variable?
On Sat, Jul 02, 2016 at 08:13:55PM -0400, Xu Wang wrote: > On Thu, Jun 30, 2016 at 9:10 PM, Will Yardley >wrote: > > On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote: > >> I have read the environment variables section in 'man mutt' and there > >> does not seem to be a MUTTRC environment variable. One can set using > >> -F option but sometime environment variable is nice. > > > > What kind of uses did you have in mind? > > > > You can use environment variables in config files, so you can always > > work around this for most of the use cases I can think of by having > > > > source ~/.muttrc-$FOO > > in ~/.muttrc, and then define $FOO. > For me it is not ideal because when I execute > source ~/.muttrc-$FOO > then the rest of the .muttrc is still processed. I would like to > process only ~/.muttrc-$FOO. > I hope that has sense. I get what you're saying. But if I'm understanding what you're trying to do, you should be able to have .muttrc *only* contain: source ~/.muttrc-$FOO that is, it would be a meta-muttrc. You can still source other files from .muttrc-$FOO. w
Re: [SPAM?] Re: no MUTTRC environment variable?
On 02Jul2016 20:13, Xu Wangwrote: On Thu, Jun 30, 2016 at 9:10 PM, Will Yardley wrote: On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote: I have read the environment variables section in 'man mutt' and there does not seem to be a MUTTRC environment variable. One can set using -F option but sometime environment variable is nice. Can someone confirm this is correct? Is there a reason for this? What kind of uses did you have in mind? You can use environment variables in config files, so you can always work around this for most of the use cases I can think of by having source ~/.muttrc-$FOO in ~/.muttrc, and then define $FOO. Thank you for responding. That is good tricky to know. You said "for most of the use cases I can think of". What is the use case you can think of where the tricky above will not function? For me it is not ideal because when I execute source ~/.muttrc-$FOO then the rest of the .muttrc is still processed. I would like to process only ~/.muttrc-$FOO. I hope that has sense. What about this: .muttrc source .muttrc-$FOO .muttrc-default all your normal settings and set $FOO (well, probably something like $MUTT_PROFILE_NAME) to 'default' in your .profile. That way your .muttrc runs only the .muttrc-whatever you ask for, and by default runs your normal settings. Cheers, Cameron Simpson
Re: Delete all threads which are incomplete?
On 02-07-2016 21:59:22, Francesco Ariis wrote: > On Sat, Jul 02, 2016 at 06:23:38PM +0200, Matthias Beyer wrote: > > This is awesome! I removed the "~l~N" part as well as "" for my > > setup. The former so I can apply it everywhere and the latter so I can > > see what I did to make this work and learn from it. > > Dabbling with mutt during half-time, I see ;) > Glad it was of help! half-time? What do you mean? -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. signature.asc Description: PGP signature
Re: Delete all threads which are incomplete?
On Sat, Jul 02, 2016 at 06:23:38PM +0200, Matthias Beyer wrote: > This is awesome! I removed the "~l~N" part as well as "" for my > setup. The former so I can apply it everywhere and the latter so I can > see what I did to make this work and learn from it. Dabbling with mutt during half-time, I see ;) Glad it was of help!
Re: Delete all threads which are incomplete?
Hi, On 02-07-2016 14:57:53, Francesco Ariis wrote: > On Sat, Jul 02, 2016 at 02:03:58PM +0200, Matthias Beyer wrote: > > Hi, > > > > is it possible with mutt to delete all mail threads where messages are > > missing (aka the first message in the thread is a response to a > > message which is not in the mailbox)? > > > > If yes, how to do this? > > Ah! my time to shine > > http://www.ariis.it/static/articles/mutt-ml/page.html > > tl;dr: play around with > > macro index d "~l~N(!~(!~x.+))(!~(~F))" > > and see if you like it This is awesome! I removed the "~l~N" part as well as "" for my setup. The former so I can apply it everywhere and the latter so I can see what I did to make this work and learn from it. Thank you very much! -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. signature.asc Description: PGP signature
Re: Delete all threads which are incomplete?
On Sat, Jul 02, 2016 at 02:03:58PM +0200, Matthias Beyer wrote: > Hi, > > is it possible with mutt to delete all mail threads where messages are > missing (aka the first message in the thread is a response to a > message which is not in the mailbox)? > > If yes, how to do this? Ah! my time to shine http://www.ariis.it/static/articles/mutt-ml/page.html tl;dr: play around with macro index d "~l~N(!~(!~x.+))(!~(~F))" and see if you like it -F
Delete all threads which are incomplete?
Hi, is it possible with mutt to delete all mail threads where messages are missing (aka the first message in the thread is a response to a message which is not in the mailbox)? If yes, how to do this? -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg. signature.asc Description: PGP signature