On 2020-12-16 19:36, David Champion wrote:
As Kevin mentioned, I have some patches that work to resolve this
stuff
* Upcoming code supports X-Label, X-Keywords, X-Mozilla-Keys, and
Keywords.
* Mutt will read keywords from any of these and, by default, write them
back to the same
* On 16 Dec 2020, Orm Finnendahl wrote:
> Hi,
>
> trying to pass the mail text from the index or pager to an external
> script (e.g. using the "|" keystroke on a mail in the index) it seems,
> it's not the text which gets piped, but rather the string
> "HASH(0x5652badff508)".
That looks like
Sorry for top-posting, the quoted stuff below is relevant but I don't want
to respond point by point.
As Kevin mentioned, I have some patches that work to resolve this
stuff. They're up to date as of Mutt 2.0, and I hope to work on merging
over the next few weeks (winter break in the US).
A
On Wed, Dec 16, 2020 at 02:35:00PM -0500, Kurt Hackenberg wrote:
How does Mutt handle this through IMAP? The protocol knows about
keywords.
Mutt uses the message header for all backends. IMAP Flag keywords are
used internally for setting 'old' on messages, but aren't exposed
otherwise.
--
16/12/20 21:35 ನಲ್ಲಿ, Orm Finnendahl
ಬರೆದರು:
>
> Hi,
>
> trying to pass the mail text from the index or pager to an external
> script (e.g. using the "|" keystroke on a mail in the index) it seems,
> it's not the text which gets piped, but rather the string
> "HASH(0x5652badff508)".
Hmm, I
Hi,
trying to pass the mail text from the index or pager to an external
script (e.g. using the "|" keystroke on a mail in the index) it seems,
it's not the text which gets piped, but rather the string
"HASH(0x5652badff508)".
I'm pretty sure it worked before, but I don't know whether it's
I use multiple space separated labels using only one X-label field to
locally to classify my emails. I limit them with ~y and made some
scripts to assign/edit them.
Regards,
Luis
On Wed, Dec 16, 2020 at 03:42:07PM +0100, Marcus C. Gottwald wrote:
>
> Dear fellow Mutt users,
>
> I have incoming
On 2020-12-16 13:05, Kevin J. McCarthy wrote:
Mutt's label handling is pretty basic right now. It expects only a
single X-Label header in the email. When editing the label, Mutt only
knows how to write a single X-Label header back.
...
The label completion has some code to delimit by ":" or
On Wed, Dec 16, 2020 at 03:42:07PM +0100, Marcus C. Gottwald wrote:
I have incoming email messages which get multiple labels assigned
by "procmail" piping through "formail -A", adding an "X-Label"
header line for each label.
Mutt fetches those email messages via IMAP and appears to be
looking
16/12/20 15:29 ನಲ್ಲಿ, ಚಿರಾಗ್ ನಟರಾಜ್ ಬರೆದರು:
>
> 16/12/20 07:23 ನಲ್ಲಿ, Felix Finch ಬರೆದರು:
> >
> > On 20201216, Felix Finch wrote:
> > >I don't know the syntax of the X-Label header, but I manually added
> > >"X-Label: One, Two, Three" to this mess
16/12/20 07:23 ನಲ್ಲಿ, Felix Finch ಬರೆದರು:
>
> On 20201216, Felix Finch wrote:
> >I don't know the syntax of the X-Label header, but I manually added
> >"X-Label: One, Two, Three" to this message, in case that is a useful
> >experiment.
>
> Rats. Mut
On 20201216, Felix Finch wrote:
I don't know the syntax of the X-Label header, but I manually added "X-Label: One,
Two, Three" to this message, in case that is a useful experiment.
Rats. Mutt stripped my fake X-Label: header right away; even the local Fcc:
copy do
On 20201216, Marcus C. Gottwald wrote:
What's the recommended way to deal with multiple labels assigned
to an email message? Can I make Mutt look at the values of all
X-Label header lines? Should I change the procmail recipes to
append (or prepend) additional labels to an existing X-Label
header
Dear fellow Mutt users,
I have incoming email messages which get multiple labels assigned
by "procmail" piping through "formail -A", adding an "X-Label"
header line for each label.
Mutt fetches those email messages via IMAP and appears to be
looking at only the last X-Label header line when
14 matches
Mail list logo
