feature req: "Move read messages to ..."

Dear mutt devs, The message "Move read messages to ..." that appears when leaving a mailbox and 'move' is set is useful. But upon deciding to move read message I often find myself wondering how many messages mutt wants to move, as in: will it move the one message I know I read and I expect it

Re: mutt: Add message count to $move quadoption prompt.

Add message count to $move quadoption prompt. > > Display the number of messages that will be moved in the quadoption > prompt, which might prove helpful for some people. > > Thank you to Daan van Rossum for suggesting the improvement. > > diffs (13 lines): > > diff

Re: feature req: "Move read messages to ..."

McCarthy wrote: > > > On Fri, Nov 10, 2017 at 01:12:55PM +0100, Daan van Rossum wrote: > > > > 2. add to status_format a sequence like: > > > > %R number of read messages > > > > > > This one I'm not enthused about. The count used ab

isolate hang in SMTP delivery

Dear mutt devs, I occasionally experience a perpetual hang in mutt when sending email using SMTP over an unstable connection (4G). How can I best debug and isolate the cause of the issue? Or would you recommend avoiding mutt's built-in SMTP functionality? I use mutt 1.9.4. Thanks, Daan sig

Re: isolate hang in SMTP delivery

* on Friday, 2018-04-06 12:34 -0700, Kevin J. McCarthy wrote: > On Fri, Apr 06, 2018 at 08:23:59PM +0200, Daan van Rossum wrote: > > I occasionally experience a perpetual hang in mutt when sending email > > using SMTP over an unstable connection (4G). > > > > How c

invert the "abort-noattach" question

Dear mutt devs, The abort_noattach feature that was added in mutt 1.10 is useful but counter-intuitive. You expect a "do you wish to continue" question and automatically answer "N", which results in accidentally sending the email without attachment. I learned to be really careful with this qu

Re: meaning of number of lines in the message (%l in index_format)

* on Wednesday, 2019-06-26 09:13 +0200, Moritz Barsnick wrote: > > > hard to see the difference between 1.3k and 1.3M at a quick glimpse > > > across the index. > > > > Yes, perhaps the reason I do not use %c. And the fact that the > > scaling facteur is on the right instead of the left makes th

LC_TIME affects mutt's charset value

With the following locale variables set # env | grep -e LANG -e LC_ LANG=en_US.UTF-8 LC_TIME=en_DE.UTF-8 Mutt sets charset to "us-ascii" # mutt :set &charset ?charset charset="us-ascii" Now, when I do not set LC_TIME mutt sets charset to "utf-8"

[pager] line wrapping breaks URL detection

Dear mutt devs, In modern terminals that support URL detection (e.g. alacritty, foot, urxvt), it is unfortunate that mutt's internal pager inserts explicit line breaks, breaking URLs as they get wrapped. I was wondering: is there a good reason for not letting the terminal wrap lines? Best, Daa

Re: [pager] line wrapping breaks URL detection

* on Friday, 2022-05-13 11:39 +0200, Ludolf Holzheid wrote: > I think this is because Mutt needs to exactly know the terminal row it > is printing on. I'm not sure if all terminals behave the same if, for > example, the line is exactly as long as the terminal is wide. I suppose if mutt estimat

Re: [pager] line wrapping breaks URL detection

* on Friday, 2022-05-13 19:49 +0200, Vincent Lefevre wrote: > On 2022-05-13 18:49:04 +0200, Gero Treuner wrote: > > Good point. There is the good old urlview program, also mentioned in the > > Mutt manual: > > https://github.com/sigpipe/urlview > > > > It can start a browser, but doesn't present

Re: [pager] line wrapping breaks URL detection

* on Friday, 2022-05-13 18:14 +0200, Ludolf Holzheid wrote: > On Fri, 2022-05-13 17:21:37 +0200, Daan van Rossum wrote: > > > > I suppose if mutt estimates the row number incorrectly: > > 1. underestimates: you could then still overwrite the last two rows with >