googly.negotiator...@aceecat.org (2025/04/16 21:11 -0700):
> On Sat, Apr 05, 2025 at 10:35:32AM -0700, googly.negotiator...@aceecat.org
> wrote:
>
> > Can I make this a feature request?
>
> https://gitlab.com/muttmua/mutt/-/issues/499
Awesome, thanks!
Seb.
On Sat, Apr 05, 2025 at 10:35:32AM -0700, googly.negotiator...@aceecat.org
wrote:
> Can I make this a feature request?
https://gitlab.com/muttmua/mutt/-/issues/499
--
Ian
googly.negotiator...@aceecat.org (2025/04/05 10:35 -0700):
> I have accessibility issues of my own, so I definitely get your point
> and I'll think hard about it.
Thanks!
> (This article has the conventional prefix
> by a special dispensation.)
And thanks for that, too.
> In fact I also wish th
On Sat, Apr 05, 2025 at 01:03:35PM +0200, Sébastien Hinderer wrote:
> > And to think of it, I'm starting to feel the same about Re and its
> > siblings as I do about the tags. With any decent MUA you know that
> > the article is a reply or followup by its position in the
> > thread. So Re is just
googly.negotiator...@aceecat.org (2025/04/03 09:52 -0700):
> > Btw your subject field does not have the Re: at its beginning,
> > I find it surprising. :)
>
> Right, I know. This is a long story and not very mutt related
> but I think the traffic will allow for it :)
Thanks for having taken the t
googly.negotiator...@aceecat.org (2025/04/02 11:17 -0700):
> FWIW I feel any use of Bcc by a receiving MUA is broken, because it
> should never be there in the first place. And of course the sending
> software (whether the original sender or the list server) is broken
> for having left it in there.
On Thu, Apr 03, 2025 at 11:23:00AM -0700, Will Yardley wrote:
> On Thu, Apr 03, 2025 at 09:52:51AM -0700, googly.negotiator...@aceecat.org
> wrote:
[Some text about the Re: prefix in email Subject headers]
> Mutt has some builtin support for handling / cleaning that up IIRC, via
> the $reply_regex
On Thu, Apr 03, 2025 at 09:52:51AM -0700, googly.negotiator...@aceecat.org
wrote:
> But the thing is, in the course of following up with MUAs which
> implement replies differently, the tags can -- and do -- become
> intermixed with the Re prefix, and with the alternative prefixes in
> other langua
On Wed, Apr 02, 2025 at 08:44:15PM +0200, Sébastien Hinderer wrote:
> Btw your subject field does not have the Re: at its beginning,
> I find it surprising. :)
Right, I know. This is a long story and not very mutt related
but I think the traffic will allow for it :)
I edit my emails in emacs wit
No worries, it may very well be that I have not been clear enough.
Btw your subject field does not have the Re: at its beginning,
I find it surprising. :)
Seb.
On Wed, Apr 02, 2025 at 08:23:38PM +0200, Sébastien Hinderer wrote:
> > FWIW I feel any use of Bcc by a receiving MUA is broken, because
> > it should never be there in the first place. And of course the
> > sending software (whether the original sender or the list server)
> > is broken for having
On Tue, Apr 01, 2025 at 11:11:38PM +0200, Sébastien Hinderer wrote:
> > Short of rewriting the headers, not sure if there's a good fix for
> > the case where the list is BCCd, at least as things work now.
> Yeah that's where I am, too. Sure, rewriting the headers would make
> me more independent,
Will Yardley (2025/04/01 13:58 -0700):
> On Tue, Apr 01, 2025 at 09:15:19PM +0200, Sébastien Hinderer wrote:
> > Apparently the content of my index_format varies from folder to folder.
> > I also use %Z but I think, after having studied Mutt's documentation,
> > that I do understand the problem. Th
On Tue, Apr 01, 2025 at 09:15:19PM +0200, Sébastien Hinderer wrote:
> Apparently the content of my index_format varies from folder to folder.
> I also use %Z but I think, after having studied Mutt's documentation,
> that I do understand the problem. The manual says:
>
> %L If an address in the “To
Hey Will,
Many thanks for your help.
Apparently the content of my index_format varies from folder to folder.
I also use %Z but I think, after having studied Mutt's documentation,
that I do understand the problem. The manual says:
%L If an address in the “To:” or “Cc:” header field matches an add
On Tue, Apr 01, 2025 at 07:24:51PM +0200, Sébastien Hinderer wrote:
> Will Yardley (2025/03/31 23:15 -0700):
> > On Tue, Apr 01, 2025 at 07:51:52AM +0200, Sébastien Hinderer wrote:
> > > I notice that mutt does not identify a mailing list to which I am
> > > subscribed as expected.
> > >
> > > In
Will Yardley (2025/03/31 23:15 -0700):
> On Tue, Apr 01, 2025 at 07:51:52AM +0200, Sébastien Hinderer wrote:
> > I notice that mutt does not identify a mailing list to which I am
> > subscribed as expected.
> >
> > In Mutt's configuration, I used the content of the List-Post header as
> > paramete
On Tue, Apr 01, 2025 at 07:51:52AM +0200, Sébastien Hinderer wrote:
> I notice that mutt does not identify a mailing list to which I am
> subscribed as expected.
>
> In Mutt's configuration, I used the content of the List-Post header as
> parameter of the subscribe command.
>
> However, mutt does
Dear all,
I notice that mutt does not identify a mailing list to which I am
subscribed as expected.
In Mutt's configuration, I used the content of the List-Post header as
parameter of the subscribe command.
However, mutt does not display the 'L' flag I would like to see for
messages coming from
19 matches
Mail list logo
