On Tue, Feb 18, 2025 at 01:21:26PM -0500, Jude DaShiell wrote:
> Why doesn't mutt ignore User-Agent: or should that be saved as ignore
> User-Agent?
Hard to say without seeing your config(s)..
By default, looks like mutt will include User-Agent and X-Mailer (which
to me, seems like a reasonable
Why doesn't mutt ignore User-Agent: or should that be saved as ignore
User-Agent?
On Thu, Apr 11, 2024 at 02:35:30PM -0700, googly.negotiator...@aceecat.org
wrote:
> On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> - if the mailing list does mess with msgid, it absolutely must do it
> consistently for all copies of the message.
For existing software that
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin
> wrote:
>
> > On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> > > Question, what should I write in .muttrc to make my outgoing
&
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> > > Question, what should I write in .muttrc to make my outgoing
> > > mails have the same beautiful message-ID as Yandex mail?
> > The unfathomable thing about this question is why you (or anyone
On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin
wrote:
> On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> > Question, what should I write in .muttrc to make my outgoing mails have
> > the same beautiful message-ID as Yandex mail?
>
> The unfathomable thin
On Wed, Apr 10, 2024 at 01:05:09PM +0800, Kevin J. McCarthy wrote:
> On Tue, Apr 09, 2024 at 09:33:06AM -0700, Will Yardley wrote:
> > side note: using quotes around the template screws things up, that is,
> > set message_id_format=""
> > vs
> > set message_id_format=
> >
> > results in a broken m
Thanks everyone for the replies and discussion, something to ponder.
Всем спасибо за ответы и дискуссию, есть над чем поразмышлять.
On Tue, Apr 09, 2024 at 09:33:06AM -0700, Will Yardley wrote:
side note: using quotes around the template screws things up, that is,
set message_id_format=""
vs
set message_id_format=
results in a broken message-id with the quotes inside the angle brackets
(Message-ID: <"xyz">)
That shouldn't
On 09Apr2024 07:11, Michael Kjörling wrote:
On 9 Apr 2024 07:32 +1000, from c...@cskk.id.au (Cameron Simpson):
_Or_ you could "set sendmail=" to a script of your own to add a
message-id
header - that is what mutt uses to deliver the message to a mail system -
you could add a header there then
Cameron Simpson wrote:
> On 07Apr2024 13:19, Ебрашка wrote:
> > Question, what should I write in .muttrc to make my outgoing mails have
> > the same beautiful message-ID as Yandex mail?
> > For example Message-Id: <43265...@example.com> consisting of random
> &
On Tue, Apr 09, 2024 at 09:25:56AM -0700, Will Yardley wrote:
> On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> > If so that feature may not be working correctly...
>
> That is the old format for the mutt version I'm using. The new format
> looks like
>
>
>
> Thought you were on
On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> > I think some people mentioned some minor threading issues with the new
> > format?
>
> Is that so? I don't recall noticing anything about that... I'd love a
> pointer to some details, if anyone has that.
It's possible that it was
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails
> have the same beautiful message-ID as Yandex mail?
Talk about bikeshedding :-)
--
Ian
On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> On Tue, Apr 09, 2024 at 08:05:06AM -0700, Will Yardley wrote:
> > On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> > > The unfathomable thing about this question is why you (or anyone)
> > > s
On Tue, Apr 09, 2024 at 08:05:06AM -0700, Will Yardley wrote:
> On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> > The unfathomable thing about this question is why you (or anyone)
> > should care in the slightest what your message ID looks like.
>
> That&
On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> The unfathomable thing about this question is why you (or anyone)
> should care in the slightest what your message ID looks like.
That's totally true, but I still like the classic Mutt message-id
format. Maybe it'
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails have
> the same beautiful message-ID as Yandex mail?
The unfathomable thing about this question is why you (or anyone)
should care in the slightest what your mess
On 9 Apr 2024 07:32 +1000, from c...@cskk.id.au (Cameron Simpson):
> You could (a) turn on "set edit_headers=yes" so the headers are visible in
> your message and (b) have your editor startup make one?
This is what I do in order to have a UUID message-ID, which Mutt
doesn't support natively.
> _
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails have
> the same beautiful message-ID as Yandex mail?
> For example Message-Id: <43265...@example.com> consisting of random
> digits and domain name
On 07Apr2024 13:19, Ебрашка wrote:
Question, what should I write in .muttrc to make my outgoing mails have
the same beautiful message-ID as Yandex mail?
For example Message-Id: <43265...@example.com> consisting of random
digits and domain name
I think it would be enough to supply yo
On 07Apr2024 18:23, Anton Sharonov wrote:
On Sun, Apr 07, 2024 at 09:23:07AM -0600, Charles Cazabon via Mutt-users wrote:
There's a good reason for that; it help to ensure uniqueness, which
prevents
problems with threading. By limiting itself to only digits, Yandex's IDs are
much more likely
On 7 Apr 2024 18:23 +0200, from anton.sharo...@gmail.com (Anton Sharonov):
>>> For example Message-Id: <43265...@example.com> consisting of random
>>> digits and domain name
>>
>> There's a good reason for that; it help to ensure uniqueness, which prevents
>> problems with threading. By limiting
On Sun, Apr 07, 2024 at 09:23:07AM -0600, Charles Cazabon via Mutt-users wrote:
> Ебрашка wrote:
> > my mails have Message-ID: . Question, what
> > should I write in .muttrc to make my outgoing mails have the same beautiful
> > message-ID as Yandex mail?
>
> My firs
Ебрашка wrote:
> my mails have Message-ID: . Question, what
> should I write in .muttrc to make my outgoing mails have the same beautiful
> message-ID as Yandex mail?
My first question would be, why do you care what the Message-ID: field
contents look like? Virtually no-one will eve
Message-Id: <254061712447...@mail.yandex.ru> - this is how Message-Id
looks like when I receive an e-mail sent from Yandex mail web interface.
When I send a mail via mutt with activated option set hostname =
example.com, my mails have Message-ID: .
Question, what should I write in .muttrc t
n.cc/~zack/blog/posts/2011/01/how_to_use_Notmuch_with_Mutt/
3. https://wiki.archlinux.org/title/Notmuch#Integrating_with_mutt
4. http://lists.mutt.org/pipermail/mutt-users/Week-of-Mon-20221219/004044.html
[]'s
Marcelo
On 21/12/22 at 11:43, Ranjan Maitra wrote:
Hi,
My apologies for a perhaps un
On 12/21 11:43, Ranjan Maitra wrote:
> Hi,
>
> My apologies for a perhaps unrelated mutt question: I would like to search
> for a word "word" across the body of the emails of all my mutt folders. How
> do I do this? I have notmuch-mutt installed.
Ranjan,
Is the issue
Hi,
My apologies for a perhaps unrelated mutt question: I would like to search for
a word "word" across the body of the emails of all my mutt folders. How do I do
this? I have notmuch-mutt installed.
Many thanks and best wishes,
Ranjan
> Oh, I meant less efficient because the evaluation is done every time the key
> is pressed when using the macro. Plus it's a macro executing a
> which is evaluating MuttLisp.
Oh, of course! You are right.
What was I thinking? Maybe I should stop tweaking my mutt config and go to
bed? :-)
Th
On Tue, Dec 06, 2022 at 10:08:04PM +0100, Andy Spiegl wrote:
Well, you could try putting the keybindings such as
Sure, but weren't we talking about efficency, i.e. without Muttlisp? :-)
Oh, I meant less efficient because the evaluation is done every time the
key is pressed when using the mac
> Sorry I wasn't clear enough.
Now I understood it. Thank you very much!
> Well, you could try putting the keybindings such as
Sure, but weren't we talking about efficency, i.e. without Muttlisp? :-)
Thanks,
Andy
--
The brain is a wonderful organ; it starts working the moment you get up
in
On Tue, Dec 06, 2022 at 08:47:27PM +0100, Andy Spiegl wrote:
The muttlisp can't be inside quotes, so I removed the outer single
quotes.
Is this only true for "bind" lines?
Because in the macro the muttlisp code is inside quotes:
macro index j 'run (if (equal $sidebar_visible "yes") \
Kevin, thanks a lot!
This was exactly what I was looking for.
> The muttlisp can't be inside quotes, so I removed the outer single
> quotes.
Is this only true for "bind" lines?
Because in the macro the muttlisp code is inside quotes:
> macro index j 'run (if (equal $sidebar_visible "yes") \
>
On Mon, Dec 05, 2022 at 04:12:01PM -0800, Kevin J. McCarthy wrote:
set muttlisp_inline_eval
bind index j (if (equal $sidebar_visible "yes") \
'sidebar-next' \
'next-undeleted')
I realized after I sent that you might be wanting to dynamically
d
On Tue, Dec 06, 2022 at 12:24:58AM +0100, Andy Spiegl wrote:
I'm trying to bind the "j" key to the function "sidebar-next" if the sidebar is
visible.
The only doable way seems to be using muttlisp.
I tried to follow the example in the mutt manual but I'm failing to write this
tiny piece of lisp
Good evening,
I'm trying to bind the "j" key to the function "sidebar-next" if the sidebar is
visible.
The only doable way seems to be using muttlisp.
I tried to follow the example in the mutt manual but I'm failing to write this
tiny piece of lisp code.
Could someone help me please to correct t
On Mon, Oct 25, 2021 at 08:13:15PM -0400, John Hawkinson wrote:
> Derek Martin wrote on Mon, 25 Oct 2021
> at 19:00:12 EDT in <20211025230012.gc9...@bladeshadow.org>:
>
> > Cost? I see no cost, other than the time needed to physically check
>
> My Oct. 7 email, to which you replied, enumerated
Derek Martin wrote on Mon, 25 Oct 2021
at 19:00:12 EDT in <20211025230012.gc9...@bladeshadow.org>:
> Cost? I see no cost, other than the time needed to physically check
My Oct. 7 email, to which you replied, enumerated several costs that I
perceived.
That you go on to state that you perceive n
On Thu, Oct 07, 2021 at 11:52:02PM -0400, John Hawkinson wrote:
> ಚಿರಾಗ್ ನಟರಾಜ್ wrote on Thu, 7 Oct 2021
> at 23:32:00 EDT in :
>
> > Any email client (including mobile email clients) worth its salt is
> > going to wrap the subject line (at least in the email view, if not
> > in the index view),
On Fri, Oct 08, 2021 at 06:50:24PM +1100, raf wrote:
> My advice is, don't worry about the default.
> If you don't like it, just change it.
>
> "man muttrc" and look for "forward_format".
>
> I think you want something like this in your ~/.muttrc:
>
> set forward_format = "Fwd: %s"
>
> or:
My advice is, don't worry about the default.
If you don't like it, just change it.
"man muttrc" and look for "forward_format".
I think you want something like this in your ~/.muttrc:
set forward_format = "Fwd: %s"
or:
set forward_format = "FW: %s"
They are both common patterns.
And they
So, in my opinion, communication is most effective if the recipient easily
comprehends what is conveyed to him/her. I suspect most recipients of our
e-mails do not know much about mutt except that you likely get it from a place
other than a breeder.
So, [mutt-users@mutt.org: Email Subject] make
rwarding look like
> Outlook's" or whatever. But I think a much more compelling case is required
> to change the default.
>
> Of course, others may disagree.
I think this gets to the crux of the disagreement. Your assumption is "No one
is practically going to be confu
ಚಿರಾಗ್ ನಟರಾಜ್ wrote on Thu, 7 Oct 2021
at 23:32:00 EDT in :
> Any email client (including mobile email clients) worth its salt is
> going to wrap the subject line (at least in the email view, if not
> in the index view), so that shouldn't really be an issue, right?
My principal concern is with
12021/06/39 09:52.97 ನಲ್ಲಿ, John Hawkinson ಬರೆದರು:
> I'd object to the proposal to add the "FW: " characters to the default. Space
> is at a premium in modern Subject lines, especially with the prevalence of
> mobile devices that have limited screen real estate, and cutting out 3
> characters i
I'd object to the proposal to add the "FW: " characters to the default.
Space is at a premium in modern Subject lines, especially with the
prevalence of mobile devices that have limited screen real estate, and
cutting out 3 characters is very undesirable. I think it's pretty clear
from context that
12021/06/39 09:27.23 ನಲ್ಲಿ, Globe Trotter via Mutt-users
ಬರೆದರು:
> When I foward my mutt-composed email, I have something like the following,
> which I believe is the default behaviour:
>
> [mutt-users@mutt.org: Email subject]
>
> which I think is very nice because it gives the recipient an id
When I foward my mutt-composed email, I have something like the following,
which I believe is the default behaviour:
[mutt-users@mutt.org: Email subject]
which I think is very nice because it gives the recipient an idea of whether
the originator of this email is someone s/he should even bother
> I think that might be elinks. I'm not sure about what all the relevant
> options are, but document.colors.text (default foreground) may be what
> is giving you light gray text. You probably also want
> document.colors.use_document_colors to be 2 and document.css.enable to
> be enabled (1)?
Tha
On 2021-07-21, isdtor wrote:
> I realize my config has a lot of moving parts and non-default
> settings, but I still hope someone can shine a light on this.
>
> I use less instead of the internal pager (note -R option),
>
> set pager="less -eiMR"
>
> and elinks for html display
>
> text/html; /usr
I realize my config has a lot of moving parts and non-default settings, but I
still hope someone can shine a light on this.
I use less instead of the internal pager (note -R option),
set pager="less -eiMR"
and elinks for html display
text/html; /usr/bin/elinks -localhost 1 -no-connect 1 -for
On 11Dec2020 07:27, Tom Tunguz wrote:
>Suppose I'd like to move the address in the to field to the bcc field.
>How do I do that?
With a macro. Not sure it is possible.
I have:
set edit_headers=yes
in my config and do all of that when editing the message.
Cheers,
Cameron Simpson
Amazing. Thank you so much, Anders and Francesco.
One more question if you don't mind.
Suppose I'd like to move the address in the to field to the bcc field. How
do I do that?
On Thu, Dec 10, 2020 at 8:57 PM Francesco Ariis wrote:
> Hello Tom,
>
> Il 10 dicembre 2020 alle
Hello Tom,
Il 10 dicembre 2020 alle 20:11 Tom Tunguz ha scritto:
> Hi,
>
> I'm just getting into mutt and really enjoying it. I'm trying to create a
> macro to add someone to the cc window that appears after closing the editor
> (vim in my case) and mutt shows the to, cc, BCC, subject fields. I'd
* Tom Tunguz [2020-12-10 20:11:47 -0800]:
Hi,
I'm just getting into mutt and really enjoying it. I'm trying to create a
macro to add someone to the cc window that appears after closing the editor
(vim in my case) and mutt shows the to, cc, BCC, subject fields. I'd like
to hit control + g and a
Hi,
I'm just getting into mutt and really enjoying it. I'm trying to create a
macro to add someone to the cc window that appears after closing the editor
(vim in my case) and mutt shows the to, cc, BCC, subject fields. I'd like
to hit control + g and add an email address.
My current macro is this
On Thu, Nov 26, 2020 at 04:50:02PM -0500, Kurt Hackenberg wrote:
> On 2020-11-26 09:26, Chris Green wrote:
>
> > Reading the mairix man page it says that the messages found by mairix
> > are symbolic links when using maildir...
>
> Yes. Doesn't the symbolic link itself tell you where the original
On 2020-11-26 09:26, Chris Green wrote:
Reading the mairix man page it says that the messages found by mairix
are symbolic links when using maildir...
Yes. Doesn't the symbolic link itself tell you where the original
message is? What do you want to do, exactly?
Does the "muttjump" that Chri
* Chris Green on Thursday, November 26, 2020 at 12:11:10 +:
I use mairix to search my mail.
I'm sure I've asked this question before but it was a *long* time ago
and I can't remember or find the answer.
When mairix has found a message with a given string/pattern in it how
ca
* Chris Green [11-26-20 10:08]:
> On Thu, Nov 26, 2020 at 02:26:40PM +, Chris Green wrote:
> > On Thu, Nov 26, 2020 at 08:13:43AM -0500, Patrick Shanahan wrote:
> > > * Chris Green [11-26-20 07:13]:
> > > > I use mairix to search my mail.
> > > >
On Thu, Nov 26, 2020 at 02:26:40PM +, Chris Green wrote:
> On Thu, Nov 26, 2020 at 08:13:43AM -0500, Patrick Shanahan wrote:
> > * Chris Green [11-26-20 07:13]:
> > > I use mairix to search my mail.
> > >
> > > I'm sure I've asked this question b
On Thu, Nov 26, 2020 at 08:13:43AM -0500, Patrick Shanahan wrote:
> * Chris Green [11-26-20 07:13]:
> > I use mairix to search my mail.
> >
> > I'm sure I've asked this question before but it was a *long* time ago
> > and I can't remember or find th
* Chris Green [11-26-20 07:13]:
> I use mairix to search my mail.
>
> I'm sure I've asked this question before but it was a *long* time ago
> and I can't remember or find the answer.
>
> When mairix has found a message with a given string/pattern in it how
>
I use mairix to search my mail.
I'm sure I've asked this question before but it was a *long* time ago
and I can't remember or find the answer.
When mairix has found a message with a given string/pattern in it how
can I tell *where* it found it? I thought it put something
On Tue, Mar 12, 2019 at 14:06:59 +1100, Erik Christiansen wrote:
> On 11.03.19 20:32, Jason wrote:
> > To prevent this, I usually press Tab one extra time to see how many
> > matches pop up; just wondering if that's what everyone else does too or
> > if there's something that would negate the nee
On Tue, Mar 12, 2019 at 02:06:59PM +1100, Erik Christiansen wrote:
> On 11.03.19 20:32, Jason wrote:
> > To prevent this, I usually press Tab one extra time to see how many
> > matches pop up; just wondering if that's what everyone else does too or
> > if there's something that would negate the n
On 12Mar2019 14:06, Erik Christiansen wrote:
On 11.03.19 20:32, Jason wrote:
To prevent this, I usually press Tab one extra time to see how many
matches pop up; just wondering if that's what everyone else does too or
if there's something that would negate the need for the extra Tab press.
Tha
On 11.03.19 20:32, Jason wrote:
> To prevent this, I usually press Tab one extra time to see how many
> matches pop up; just wondering if that's what everyone else does too or
> if there's something that would negate the need for the extra Tab press.
That's how mailbox name completion works too.
I regularly use Tab to autocomplete alias names. Is there any way to
differentiate between a name that is partially completed (due to there
being several aliases starting with that string) and one that is
complete?
For example, say I have an alias named johndoe and another one named
johnnybrow
* David J. Weller-Fahy [2018-04-25 21:38 -0400]:
I've been dealing with an error whenever mutt starts for a few years
now, and finally decided to ask how others have fixed the issue.
#v+
folder-hook . "set record=^"
#v-
Sigh... apparently inspiration required that I send an email to a mailing
I've been dealing with an error whenever mutt starts for a few years
now, and finally decided to ask how others have fixed the issue.
I have all my sent email saved in the current mailbox. I do this using
the following setting in my muttrc (per
https://gitlab.com/muttmua/mutt/wikis/MuttFaq/Folde
On Tue, Apr 18, 2017 at 09:29:41PM +0200, Pavel Troller wrote:
> When (q)uitting, mutt 1.5.x asked for example:
> Move read messages to /home/patrol/Mail/mail.arch? ([no]/yes):
> while the new mutt just quits and to be honest, I don't know, how to
> trigger this action manually and then quit.
Try
mutt just quits and to be honest, I don't know, how to
trigger this action manually and then quit.
I know it's a stupid question, I'm using mutt for really long time
and I had never problems with it, just this one after the recent upgrade.
And I'm not able to find, what change
On Fri, May 13, 2016 at 09:13:22AM -0700, Kevin J. McCarthy wrote:
> On Fri, May 13, 2016 at 02:57:03PM +0100, Chris Green wrote:
> > I have another question regarding 1.6.1 differences from 1.5.24. In
> > my index replies to message don't show their subject line correc
On Fri, May 13, 2016 at 02:57:03PM +0100, Chris Green wrote:
> I have another question regarding 1.6.1 differences from 1.5.24. In
> my index replies to message don't show their subject line correctly,
> for example:-
>
> 18 r + 10-May-16 Jane Chevous( 83) Re
On Fri, May 13, 2016 at 05:39:04PM +0300, Alex Poslavsky wrote:
> On 05/13, Chris Green wrote:
> > I have another question regarding 1.6.1 differences from 1.5.24. In
> > my index replies to message don't show their subject line correctly,
> > for example:-
> >
I have another question regarding 1.6.1 differences from 1.5.24. In
my index replies to message don't show their subject line correctly,
for example:-
18 r + 10-May-16 Jane Chevous( 83) Reshapers
19 + 10-May-16 Jane Chevous( 179) M-b~T~TM-b~T~@>
That M-b~
El día Saturday, November 01, 2014 a las 05:06:42PM +0100, John Niendorf
escribió:
> Hello Fellow Mutters,
>
> I often have to send the same message to the same group of
> people. Specifically I send a note that a website has been updated.
> I have been doing this in Mutt using an alias that c
Hello Fellow Mutters,
I often have to send the same message to the same group of
people. Specifically I send a note that a website has been updated.
I have been doing this in Mutt using an alias that contains all of the
email address the message is sent to and then hitting a key sequence to
c
On Fri, May 23, 2014 at 07:08:42PM -0400, Guy Gold wrote:
> ===CONFIDENTIAL===
>
> On Fri, May 23, 2014 at 03:14:20PM -0500, Derek Martin wrote:
> > > I'm trying to understand if it's 'normal' (wink: Derek
Oh ah. Yes, well, being totally sober when I replied to this, I
comp
;threads, order in question
> >Thu, May 22, 2014 at 07:22:07PM EDT Cameron Simpson ├─>
> >Thu, May 22, 2014 at 08:54:23PM EDT To mutt-users@mutt.o │ └─>
> >Thu, May 22, 2014 at 09:37:48PM EDT Cameron Simpson │ └─>
> >Fri, May 23, 2014 at 08:19:11AM EDT To
Cameron's message from 7:22PM. At that point, I thought - that's
because your responding directly to my message. Then, I
refreshed my index for some other reason, and the index shifted
to what you see now:
Thu, May 22, 2014 at 05:19:42PM EDT To mutt-users@mutt.o Display of threads,
order i
right in this current thread, when I opened the
mutt mailbox, your messages, from 4:14PM, was right above
Cameron's message from 7:22PM. At that point, I thought - that's
because your responding directly to my message. Then, I
refreshed my index for some other reason, and the index shifted
to
On Fri, May 23, 2014 at 03:05:13PM -0500, David Champion wrote:
> > Thu, May 22, 2014 at 05:19:42PM EDT To mutt-users@mutt.o Display of
> > threads, order in question
> > Thu, May 22, 2014 at 07:22:07PM EDT Cameron Simpson └─>
> > Thu, May 22, 2014 at 08
Hi Guy,
On Thu, May 22, 2014 at 05:19:42PM -0400, Guy Gold wrote:
> I'm trying to understand if it's 'normal' (wink: Derek
> Martin, if you copy) to have most of my threads sorted
> not-really-through-date-received.
Why are you winking at me?
As for your question
the sort.
> It looks like, once authors of messages write to others (rather
> than replying one after another, chronologically), that's when the
> mix-up happens.
>
>
> Thu, May 22, 2014 at 05:19:42PM EDT To mutt-users@mutt.o Display of
> threads, order in question
>
Thu, May 22, 2014 at 05:19:42PM EDT To mutt-users@mutt.o Display of threads,
order in question
Thu, May 22, 2014 at 07:22:07PM EDT Cameron Simpson └─>
Thu, May 22, 2014 at 08:54:23PM EDT To mutt-users@mutt.o └─>
Thu, May 22, 2014 at 09:37:48PM EDT Cameron Simpson └─
* On 23 May 2014, Guy Gold wrote:
>
> That, pretty much, is what I'm trying to get to, only reversed,
> with the newest message, on the bottom. I wonder if other parts
> of my .muttrc breaking it.
For threading, you need sort=threads. Sort_aux is the only variable.
Reverse- and last- are modu
t,May 17 05:59:PM Karl Voit └─>
> >>>Sat,May 17 09:51:PM Cameron Simpson ├─>
> >>>Sun,May 18 02:58:AM Karl Voit│ └─>
> >>>Sat,May 17 07:02:PM Gary Johnson └─>
>
> Ok, question
├─>
>Sun,May 18 02:58:AM Karl Voit│ └─>
>Sat,May 17 07:02:PM Gary Johnson └─>
Ok, question 1: do you use %d or %D for the date field in your $index_format
string?
Importantly, %D is the message date in your local time zone. If you use %d, you
get the
rovided, ideally, the two
messages from the 18th, would be at the bottom of the thread,
with the very newest one, May 18,2:28PM as the last one listed.
> The question is: why date-received instead of date? For me, "date" is the
> relevant criterion.
Yes, it can be date
at you asked for is
sane is another matter.
The question is: why date-received instead of date? For me, "date" is the
relevant criterion.
Here's an example of how a recent thread, in this mailing
list, is presented, in my mutt index.
Sat,May 17 12:19:PM Karl Voit
Greetings, mutt users.
Here are the relevant parts from .muutrc: set sort=threads
set sort_aux=reverse-last-date-received
The above places the thread with the newest message on top,
with the next newest under it, an so on. Reading through
.muttrc, It's not the best way to sort, but, I got used
simple config which simply worked.)
> Is this a unique feature?
I don't know what other MUAs might have the feature.
> Or are there other modifiers for alias?
A little effort finds that in the F1 manual.
> Documented where?
If you've only been looking in http://www.mutt.
My question is embedded in the quoted message, below:
On 20131206_210949, Erik Christiansen wrote:
... remove text that's not relevant to my questions
> help when you are off in another mailbox, and suddenly decide to fling
> off a message. To let mutt catch that use case, and put
On Fri, Nov 22, 2013 at 20:27:47 -0500, Patrick Shanahan wrote:
> * pecon...@mesanetworks.net [11-22-13 20:10]:
> >
> > When I'm reading incoming mail in Mutt, I can save the email to a
> > different folder by pressing the 's' key. When I do this, Mutt offers a
> > suggestion of a folder name.
* pecon...@mesanetworks.net [11-22-13 20:10]:
>
> When I'm reading incoming mail in Mutt, I can save the email to a
> different folder by pressing the 's' key. When I do this, Mutt offers a
> suggestion of a folder name. This suggestion seems to be the "From:"
> header. What is the actual logi
When I'm reading incoming mail in Mutt, I can save the email to a different
folder by pressing the 's' key. When I do this, Mutt offers a suggestion of a
folder name. This suggestion seems to be the "From:" header. What is the actual
logic behind the construction of this suggestion? Where can I
Incoming from Andre Klärner:
> On Fri, Jan 18, 2013 at 08:54:34PM -0700, s. keeling wrote:
> >
> > I like to keep date stamped copies of old mutt configs in my ~/mutt.
>
> Well, I used to do so a while ago, but by now I am using a git-repository
Sadly, I'm still working on my git-foo.
> for eac
1 - 100 of 1305 matches
Mail list logo
