lease) like to use strange characters to quote
> people's messages. So I found the quote_regexp command.
[...]
> If you want to allow other characters as quotes, stick in the second
> brackets, like this one I did:
>
> set quote_regexp="^([ \t]*[%|>:}#])+"
Well, t
ssages.
You mean David, right? ;-)
> set quote_regexp="^([ \t]*[%|>:}#])+"
> Maybe this will help someone :)
Sorry, no, it doesn't. I use:
,-
| pdmef@klaus:~$ mutt -Q quote_regexp
| quote_regexp="^([ \t]*(([A-Z]+)?[|:>!#%]))+"
`-
...which will catch
Howdy Mutters,
I just want to contribute a little something I figured out.
Nothing earth shattering here, but it might help someone. Aparently
some people (ahem, no names please) like to use strange characters
to quote people's messages. So I found the quote_regexp command. The
de
On Fri, Mar 01, 2002 at 01:03:59PM -0600, Aaron Schrab wrote:
> quote_regexp is ignored for format=flowed messages since RFC 2646, which
> describes that format, mandates that only ">" characters at the very
> beginning of a line are to be considered quote characters.
At 22:02 -0500 28 Feb 2002, Andrew Pimlott <[EMAIL PROTECTED]> wrote:
> I have quote_regexp set in my .muttrc:
>
> set quote_regexp="^[[:blank:]]*([[:alnum:]]{0,10}>|[]|:}#);+]|-> )"
>
> This should match (among other things) any line with a leading &q
* Andrew Pimlott <[EMAIL PROTECTED]> [020301 11:10]:
> I'm using mutt 1.3.27i from Debian "testing". I've noticed that
> occasionally, quoted text isn't highlighted in the pager.
> I have quote_regexp set in my .muttrc: [...]
> This should match (am
I'm using mutt 1.3.27i from Debian "testing". I've noticed that
occasionally, quoted text isn't highlighted in the pager.
I have quote_regexp set in my .muttrc:
set quote_regexp="^[[:blank:]]*([[:alnum:]]{0,10}>|[]|:}#);+]|-> )"
This should m
