Re: Having problems with POP3 setup

With debugger I saw this line: "-ERR Unknown command: LAST"; so I think you were right once again... So if I wanted this function, or the one of "keep messages in server for x days", would I need another external POP3 mail fetcher? I did read in the Mutt wiki that Mutt originally didn't intend to

Postponing and forwarding

When composing an email, I decided to postpone instead of immediately send. It got saved in Drafts folder, but when deciding to send it, I opened the draft, but there's no "send" option; just the usual respond, new email, and the other options when opening any other message. Then how am I suppos

Re: Postponing and forwarding

On 2022-08-31 11:51, X Tec wrote: When composing an email, I decided to postpone instead of immediately send. It got saved in Drafts folder, but when deciding to send it, I opened the draft, but there's no "send" option; just the usual respond, new email, and the other options when opening any

Re: Postponing and forwarding

On 2022-08-31, X Tec wrote: > When composing an email, I decided to postpone instead of immediately > send. It got saved in Drafts folder, but when deciding to send it, I > opened the draft, but there's no "send" option; just the usual > respond, new email, and the other options when opening any o

Re: Postponing and forwarding

On Wed, Aug 31, 2022 at 11:51:24AM -0500, X Tec wrote: > When composing an email, I decided to postpone instead of immediately > send. It got saved in Drafts folder, but when deciding to send it, I > opened the draft, but there's no "send" option; just the usual > respond, new email, and the other

Re: Is linewrap dead?

On Mon, Aug 29, 2022 at 07:10:14AM -0400, John Hawkinson wrote: > Kurt Hackenberg wrote on Mon, 29 Aug 2022 at 02:58:32 EDT in > : > > > If you put a newline only at the end of a paragraph, it won't be > > displayed correctly by software that doesn't expect that. Such > > software will probably

Re: Is linewrap dead?

Derek Martin wrote on Wed, 31 Aug 2022 at 13:39:42 EDT in <20220831173942.gb13...@bladeshadow.org>: > It's been my experience that if you read your mail on anything other > than a phone, the 72-character line width is fine, and even on a phone > if you turn it sideways it's still fine. My prefer

Re: Is linewrap dead?

Hello everyone, Il 29 agosto 2022 alle 00:28 Tavis Ormandy ha scritto: > The problem is popular modern mobile and web-based MUAs don't handle > this and can make unexpected linewrap decisions. It's no issue when > emailing UNIX nerds, but non-nerds think I'm doing something wrong. I am quite surp

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 12:39:42PM -0500, Derek Martin wrote: I can't say I know how various MTAs handle lines longer than 998 characters, but I would expect at least a subset would either truncate them or reject your message... or at least that it would be wise to assume so. Mail readers th

Re: Is linewrap dead?

Francesco Ariis wrote on Wed, 31 Aug 2022 at 13:57:43 EDT in : > I do not have a smartphone, can I ask someone to provide a .png on > how this or other similar messages look on a smartphone client? I am > very curious and hopefully a definite guideline will pop up from this I sent a previous ver

Re: Is linewrap dead?

John, Il 31 agosto 2022 alle 14:05 John Hawkinson ha scritto: > Here's an inlined PNG showing how your email displayed for me in the > Android Gmail app. > Note the short lines like "clients my emails" and "provide a .png on". It > could certainly be worse (and it often is), but it's not great: m

Re: Is linewrap dead?

On 2022-08-30, Jan Eden via Mutt-users wrote: > Apart from the known drawbacks of HTML mail, the markdown2html script > has a couple of requirements to further complicate my (already overly > complex) mailstack. Yep, I can understand that. I think the best option might be piping your mail through

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 01:46:49PM -0400, John Hawkinson wrote: > Derek Martin wrote on Wed, 31 Aug 2022 > at 13:39:42 EDT in <20220831173942.gb13...@bladeshadow.org>: > > > It's been my experience that if you read your mail on anything other > > than a phone, the 72-character line width is fine,

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 07:57:43PM +0200, Francesco Ariis wrote: > > The problem is popular modern mobile and web-based MUAs don't handle > > this and can make unexpected linewrap decisions. It's no issue when > > emailing UNIX nerds, but non-nerds think I'm doing something wrong. > > I do not hav

Re: Is linewrap dead?

On 2022-08-31, Derek Martin wrote: >> That'd be true if we were sending emails to ourselves >> but a lot of us send email to people who read their mail primarily >> or exclusively on phones and in desktop GUIs that don't approximate >> 72-chars. > > I don't see why this matters, because as I alread

Re: Is linewrap dead?

I don't mean to monopolize the conversation, but: Derek Martin wrote on Wed, 31 Aug 2022 at 15:48:55 EDT in <20220831194855.gc13...@bladeshadow.org>: > I don't see why this matters, because as I already pointed out, any > desktop GUI MUA will have no trouble displaying 72 character lines > wrapp

Re: Is linewrap dead?

On 2022/08/31 16:38, John Hawkinson wrote: I don't really think we're flouting the standards. Very long lines -- one line per paragraph -- changes the meaning of ASCII/Unicode. I could live with that if it were labelled, with a new MIME subtype, but I agree that a new subtype probably will

Re: Postponing and forwarding

Yes, you're all right. I should've read the manual. I owe you an apology. And thanks for your still help. On 2022-08-31 17:35:21, Sam Kuper wrote: > On Wed, Aug 31, 2022 at 11:51:24AM -0500, X Tec wrote: > > When composing an email, I decided to postpone instead of immediately > > send. It got sa

Re: Is linewrap dead?

Kurt Hackenberg wrote on Wed, 31 Aug 2022 at 17:22:48 EDT in <2d716370-8c96-adcf-11d4-939a3f808...@panix.com>: > > I don't really think we're flouting the standards. > > Very long lines -- one line per paragraph -- changes the meaning of > ASCII/Unicode. err, what? I am confused what we are di

trouble with my_hdr and $format_flowed

I've long had my mutt+vim setup to compose format=flowed email. There's just one problem: it wasn't working. So I'm digging into why. I've got: set text_flowed=yes in my setup. And if I pare down enough mutt settings, my reply goes out with this header: Content-Type: text/plain; chars

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 07:58, Cameron Simpson wrote: >I've put a format=flowed into this message by hand, and I'll see if it >survives. It did not. The message sent by mutt discarded my Content-Type header and used: Content-Type: text/plain; charset=us-ascii So I've actually got a significant proble

Re: trouble with my_hdr and $format_flowed

I have a pretty weird way of composing replies and new messages: I like to be able to detach from the new message window. So I compose in a separate tmux session. If you compose directly in mutt+vim without composing in a separate tmux window, does it work? (I would assume so, as I use mutt+vim

Re: trouble with my_hdr and $format_flowed

I forgot the my_hdr issue. This line: my_hdr "Content-Type: text/plain; charset=usascii; format-flowed" results in this from from mutt at startup: Error in /Users/cameron/rc/mutt/settings, line 129: charset=usascii: unknown command So it appears that I can't use a semicolon in my_hdr?

Re: trouble with my_hdr and $format_flowed

On 31Aug2022 18:06, David Lowry-Duda wrote: >>I have a pretty weird way of composing replies and new messages: I like >>to be able to detach from the new message window. So I compose in a >>separate tmux session. > >If you compose directly in mutt+vim without composing in a separate >tmux window,

Re: trouble with my_hdr and $format_flowed

On Thu, Sep 01, 2022 at 08:08:21AM +1000, Cameron Simpson wrote: I forgot the my_hdr issue. This line: my_hdr "Content-Type: teAxt/plain; charset=usascii; format-flowed" results in this from from mutt at startup: Error in /Users/cameron/rc/mutt/settings, line 129: charset=usascii: unknow

Re: trouble with my_hdr and $format_flowed

On Thu, Sep 01, 2022 at 08:11:50AM +1000, Cameron Simpson wrote: The essential problem is that I run a separate mutt instance using "mutt -H" on a copy of my message template. The manual does say that $text_flowed has no effect then, but I seem to have no other way to apply the needed header - ad

Re: trouble with my_hdr and $format_flowed

On 31Aug2022 15:28, Kevin J. McCarthy wrote: >The parser for my_hdr is a bit different - it allows quote characters >in the header, so it doesn't treat them specially like elsewhere. >However, semicolons are still parsed normally. Ah, right. >I think this was a mistake, but would be a breakin

Re: trouble with my_hdr and $format_flowed

On 31Aug2022 15:37, Kevin J. McCarthy wrote: >On Thu, Sep 01, 2022 at 08:11:50AM +1000, Cameron Simpson wrote: >>The essential problem is that I run a separate mutt instance using "mutt >>-H" on a copy of my message template. The manual does say that >>$text_flowed has no effect then, but I seem t

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 05:43:41PM -0400, John Hawkinson wrote: Very long lines -- one line per paragraph -- changes the meaning of ASCII/Unicode. err, what? I am confused what we are discussing. ASCII was not designed to be automatically word-wrapped. The idea was that a line keeps going

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 08:50, Cameron Simpson wrote: >>If you haven't played with it before, you might also look into >>background editing and the contrib/bgedit-screen-tmux.sh script. See >>. > >I will; the background editing feature postdated my tmux games. I don'

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 05:43:41PM -0400, John Hawkinson wrote: > John Hawkinson wrote on Wed, 31 Aug 2022 > at 16:38:11 EDT in : > > > I suppose I should send some 2,000-character paragraph emails as > > tests to see what happens, but I very much doubt there will be > > problems as a result. >

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 04:38:11PM -0400, John Hawkinson wrote: > I don't mean to monopolize the conversation, but: > > Derek Martin wrote on Wed, 31 Aug 2022 > at 15:48:55 EDT in <20220831194855.gc13...@bladeshadow.org>: > > > I don't see why this matters, because as I already pointed out, any

Re: Is linewrap dead?

Derek Martin wrote on Wed, 31 Aug 2022 at 19:35:15 EDT in <20220831233515.gf13...@bladeshadow.org>: > > I don't really think we're flouting the standards. > ... > So it IS only a recommendation, not a requirement--but it's a pretty > strong recommendation, and either way you're still flouting it

Re: Is linewrap dead?

On 2022-08-31, Tavis Ormandy wrote: > If it was up to me I'd continue using > tw=72, but sometimes a compromise > is necessary. Perhaps tw=40 would be sufficient to make everybody happy. Reminds me a bit of my old Apple, ][+ days with 40-column upper-case only. ;-) -tkc

Re: trouble with my_hdr and $format_flowed

On Thu, Sep 01, 2022 at 08:50:33AM +1000, Cameron Simpson wrote: On 31Aug2022 15:37, Kevin J. McCarthy wrote: I think this may work best for you, if the my_hdr approach doesn't work. It seems to have no effect; the Content-Type eg from my reply just now to you is still not format=flowed. I di

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 02:48:55PM -0500, Derek Martin wrote: > The bottom line is there is absolutely no reason why hard-wrapped > lines of plain text at 72 characters should ever need to display > unreadably for any desktop user, or even anyone on any reasonable > mobile device which can rotat

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 05:22:48PM -0400, Kurt Hackenberg wrote: Very long lines -- one line per paragraph -- changes the meaning of After top posting that is probably the most annoying thing on email. And from what I can tell reading this thread, there will always be some nasty software and s