I got an interesting mail from Nikola Petrov off-list saying that his
Mutt configuration does not interpret ~p as including Cc'd mails.
- In my case, if I limit to ~p, I get messages with the C flag set.
- In his case, if he limits to ~p, he (apparently) does not.
Is there some configuration opti
On Mon, Feb 10, 2014 at 05:49:55PM +0800, Chris Down wrote:
> I got an interesting mail from Nikola Petrov off-list saying that his
> Mutt configuration does not interpret ~p as including Cc'd mails.
Wouldn't it be better to keep the mails on list? Could get confusing
otherwise.
--
"If you're no
On Tue, Feb 11, 2014 at 12:03:17AM +1300, Chris Bannister wrote:
> On Mon, Feb 10, 2014 at 05:49:55PM +0800, Chris Down wrote:
> > I got an interesting mail from Nikola Petrov off-list saying that his
> > Mutt configuration does not interpret ~p as including Cc'd mails.
>
> Wouldn't it be better t
On 2014-02-11 00:03:17 +1300, Chris Bannister wrote:
> On Mon, Feb 10, 2014 at 05:49:55PM +0800, Chris Down wrote:
> > I got an interesting mail from Nikola Petrov off-list saying that his
> > Mutt configuration does not interpret ~p as including Cc'd mails.
>
> Wouldn't it be better to keep the m
On 2014-02-11 00:29:17 +1300, Chris Bannister wrote:
> In my .muttrc I have:
>
> set to_chars=" +TCF"
>
> See table 2.6 in the documentation.
How does this affect the behaviour of ~p? As far as I can tell, this
only appears to have to do with what is displayed in the status
indicator.
pgpiuFJt
On Tue, Feb 11, 2014 at 03:03:33AM +0800, Chris Down wrote:
> On 2014-02-11 00:29:17 +1300, Chris Bannister wrote:
> > In my .muttrc I have:
> >
> > set to_chars=" +TCF"
> >
> > See table 2.6 in the documentation.
>
> How does this affect the behaviour of ~p? As far as I can tell, this
> only ap
