Re: Indent string and interleaved posting (Colors)

[DGSJ]

On Sun, Jul 03, 2016 at 01:07:26PM +0200, Francesco Ariis wrote:
> 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

Grazie mille Francesco!

Yes, it helps :)

The default settings of quote_regexp is:
set quote_regexp='^([ \t]*[|>:}#])+'

So if you remove the #, it won't be considered anymore as a quote symbol,
and the text following # will be shown in the same colour than the rest of
the fresh text.

-- 
Daniel Gutierrez San Jose
GPG pub ID = E62CA038


signature.asc
Description: PGP signature

Re: no MUTTRC environment variable?

[Xu Wang]

On Mon, Jul 4, 2016 at 12:35 AM,   wrote:
> On 03Jul2016 00:50, Xu Wang  wrote:
>>
>> 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.
>
>
> And fair enough too. I suspect then that you must explicitly invoke mutt as
> needed. This:
>
>  mutt -F /dev/null -e 'source muttrc1' -e 'source muttrc2' ...
>
> is probably the cleanest way to invoke mutt without reliance on the user's
> .muttrc, and to source whatever config you intend. You can add the "-n"
> option to also bypass and system muttrc file.
>
> Does this help?
>
> Cheers,
> Cameron Simpson 

Thank you Cameron. I will think about this option and test it. I
highly appreciate your time and thoughts.

Kind regards,

Xu

Re: no MUTTRC environment variable?

[cs]

On 03Jul2016 00:50, Xu Wang  wrote:

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.


And fair enough too. I suspect then that you must explicitly invoke mutt as 
needed. This:


 mutt -F /dev/null -e 'source muttrc1' -e 'source muttrc2' ...

is probably the cleanest way to invoke mutt without reliance on the user's 
.muttrc, and to source whatever config you intend. You can add the "-n" option 
to also bypass and system muttrc file.


Does this help?

Cheers,
Cameron Simpson