On 2024-09-09 08:42 +0200, Jan Eden via Mutt-users wrote:
> Hi,
>
> this is a little off-topic, but maybe other mutt users are affected,
> too: Since upgrading to vim 9.1.700 this morning via homebrew, the
> filetype is not set automatically anymore when calling vim from mutt.
I just updated to 9
On 2024-08-31 08:22 +0200, Francesco Ariis wrote:
> I had the same problem a long time ago. This article might interesting
> to you
>
> http://ariis.it/static/articles/mutt-ml/page.html
This is perfect and it's exactly what I was looking for. I didn't know
about the ~() patterns; mutt continu
Hello and happy Friday Mutt users!
In my muttrc, I have this folder-hook to create a mailbox-specific
macro:
folder-hook '=lang' 'macro index,pager g "~N !(=s
ANN) unset
resolveN.
set resolve" "delete uninteresting messages"'
It lets me delete any new messages I receive under the 'lang' m
On 2022-03-06 13:09 +1100, Philip Rhoades wrote:
>
>
> Adding mailboxes like that would not be viable - I have:
>
> 705 primary Maildir folders
>
> and:
>
> 2,708 total Maildir folders
>
> - and they are constantly changing - Mutt needs to autodetect ALL the
> current folders somehow . .
Hello,
On 2022-03-06 04:04 +1100, Philip Rhoades wrote:
> People,
>
> I am using mutt-2.1.5-1.fc35.x86_64 with the lines below in .muttrc - but
> after much Googling, I can't get any permuations of these configs to display
> ANY folders in the sidebar - am I missing something?
>
> Thanks,
>
> P
On 2022-03-01 18:30 -0600, sunnycemet...@gmail.com wrote:
> Consider appending the macro chain with .
That works out pretty nicely indeed, thanks!
--
Akshay.
in the following fashion:
macro index - ''
Any tips or tricks on how to suppress these error messages would be
greatly appreciated!
--
Akshay Hegde
On 2020-12-29T10:14:43-0800, Kevin J. McCarthy wrote:
> On Mon, Dec 28, 2020 at 11:34:23PM -0800, Akshay Hegde wrote:
> > Is this the expected behavior, or is this a bug?
>
> This is expected behavior. Mutt only performs new mail checking in the
> index. This prevents issues s
his a bug?
I've also tried to check for any options that might control this
behavior by going through the doc, but haven't been able to find
a relevant one, except for the $timeout option.
--
Akshay Hegde
