Re: Delete all threads which are incomplete?

2016-07-03 Thread Jonas Hedman
On 16-07-02 14:57:53, Francesco Ariis wrote:
> 
> 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

I just wanted to thank you for sharing this, I found it very useful!


Regards
-- 
Jonas Hedman 

XMPP:n...@nstr.se
PGP Key: 0x5c3989e0616bb08c
Fingerprint: 8F72 C5BE AAFA B4BA 8F46  9185 5C39 89E0 616B B08C


signature.asc
Description: Digital signature


Re: Indent string and interleaved posting (Colors)

2016-07-03 Thread Francesco Ariis
On Sun, Jul 03, 2016 at 09:56:20AM +0200, DGSJ wrote:
> Hello,
> 
> I have a (small) problem with the color of the indent strings.
> I have to use the interleaved format in a working group, and we use
> symbols preceding the responses, to mark changes, comments etc.

Hello DGSJ,
I think you might want to fiddle around with `quote_regexp`.
Does that help?
-F


Re: [SPAM?] Re: [SPAM?] Re: no MUTTRC environment variable?

2016-07-03 Thread Xu Wang
On Sat, Jul 2, 2016 at 8:44 PM, Will Yardley
 wrote:
> 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
>

Thank you very much for the replies, Will and Cameron.

Yes, these workarounds work fine for my personal setup. However, I am
working on scripts that I would like to release for other users to
use. I do not want to require other users to refactor their .muttrcs
just to use the scripts. Creating user-friendsly scripts is what
motivates me.

Kind regards,

Xu


Indent string and interleaved posting (Colors)

2016-07-03 Thread DGSJ
Hello,

I have a (small) problem with the color of the indent strings.
I have to use the interleaved format in a working group, and we use
symbols preceding the responses, to mark changes, comments etc. For
example, a thread looks like:

> This is a former line of the thread, and it is coloured in blue (It is
> correct because I have set indent_string="> "

This is the last received line of the thread, and it is coloured in green
# This is also part of the las received line, it should be also green, but
# apeares in blue, as if it were and old line.

I seems that # is interpreted as a mark for something different than new
lines...

I would appreciate some ideas to fix it. Thank you in advance for your
help.

-- 
Daniel Gutierrez San Jose
GPG pub ID = E62CA038


signature.asc
Description: PGP signature