Re: trouble with my_hdr and $format_flowed
On 01Sep2022 20:18, Kevin J. McCarthy wrote: >On Fri, Sep 02, 2022 at 08:28:01AM +1000, Cameron Simpson wrote: >>and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 >>passwd to "mutt -H" is already gone. Does mutt remove it? >> >>Ah, mutt might have move it to ~/var/mutt/compose/muttedit.94328, which >>exists with the header above. >> >>Let's look at the Content-Type on this message... > >I'm not sure if it helps at this point, but I can report that I've >taken your template above and passed it to 'mutt -H' and the resulting >sent file has format=flowed in its content-type header. :-/ > >Can you try directly doing this too, outside of your tmux-editing >framework? Yes. I should have done that already. I'm running Mutt 2.2.7 (2022-08-07) BTW, not that I expect any of this to have recent changes. I'll be back after I've done some cleaner experiments. Thanks, Cameron Simpson
Re: Postponing and forwarding
On Wed, Aug 31, 2022 at 07:27:19PM +0200, Jan Eden via Mutt-users wrote: On 2022-08-31 11:51, X Tec wrote: ... Also, how can I *forward* messages to other users? Just hit f while the message is selected in the pager. An alternative to forwarding is "bouncing" using "B" rather than "f". When bouncing, the message body and the subject line are unchanged. You have no opportunity to add comments. I use it mostly for email that should have been addressed to both my wife and myself but only came to me. I bounce it to my wife and she has a clean copy as if she were addressed in the original "To:" or "Cc:" lists. -- Jon H. LaBadie j...@labadie.us 154 Milkweed Dr (540) 868-8052 (H) Lake Frederick, VA 22630(703) 935-6720 (M)
Re: trouble with my_hdr and $format_flowed
On Fri, Sep 02, 2022 at 08:28:01AM +1000, Cameron Simpson wrote: and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 passwd to "mutt -H" is already gone. Does mutt remove it? Ah, mutt might have move it to ~/var/mutt/compose/muttedit.94328, which exists with the header above. Let's look at the Content-Type on this message... I'm not sure if it helps at this point, but I can report that I've taken your template above and passed it to 'mutt -H' and the resulting sent file has format=flowed in its content-type header. :-/ Can you try directly doing this too, outside of your tmux-editing framework? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: trouble with my_hdr and $format_flowed
On 02Sep2022 08:15, Cameron Simpson wrote: >Trying that with this reply. Well, that tossed my Content-Type header and sent with: Content-Type: text/plain; charset=us-ascii I'm trying again here, for thoroughness. The source file starts like this: Content-Type: text/plain; charset=utf-8; format=flowed From: Cameron Simpson To: mutt-users@mutt.org Cc: Bcc: c...@cskk.id.au Subject: Re: trouble with my_hdr and $format_flowed Reply-To: In-Reply-To: and the Content-Type is not presented in this current editor. Interestingly, the process tree looks like this: cameron 94359 1116 4299624 1220 \_ /bin/sh ~/bin/rmafter ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 mutt -e set editor=vim-flowed -e unset signature -e set sidebar_visible=no -H ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 cameron 94361 94359 4345688 11628 \_ mutt -e set editor=vim-flowed -e unset signature -e set sidebar_visible=no -H ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 cameron 94383 94361 4403212 12656 \_ vim -c silent 1,/^$/s/ *$// -c set filetype=mail -c set formatoptions=walqj ~/var/mutt/mutt-fleet2-501-94361-4463746866273406678 and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 passwd to "mutt -H" is already gone. Does mutt remove it? Ah, mutt might have move it to ~/var/mutt/compose/muttedit.94328, which exists with the header above. Let's look at the Content-Type on this message... Cheers, Cameron Simpson
Re: trouble with my_hdr and $format_flowed
On 01Sep2022 09:09, Kevin J. McCarthy wrote: >On Wed, Aug 31, 2022 at 06:45:08PM -0700, Kevin J. McCarthy wrote: >>In my testing, a header 'Content-Type: text/plain; format=flowed' in >>the draft file does result in the sent email being format=flowed. > >My example wasn't great: you *should* add a charset parameter set to >your system charset (I'm assuming that's utf-8). Trying that with this reply. Cheers, Cameron Simpson
Re: Is linewrap dead?
It not worked as expected https://pasteboard.co/ZP492mei7cBc.jpg Marcelo Enviado a partir de dispositivo móvel Em qui., 1 de set. de 2022 16:42, Marcelo Laia escreveu: > Hi José Maria, > > I am doing a test. > > In this message, I seted in vimrc this lines: > > > set wrap > set linebreak > > Here, I will post a lot off words to test. > > Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod > tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim > veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea > commodo consequat. Duis aute irure dolor in reprehenderit in voluptate > velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint > occaecat cupidatat non proident, sunt in culpa qui officia deserunt > mollit anim id est laborum. > > Marcelo > > On 29/08/22 at 09:59, José María Mateos wrote: > > On Mon, Aug 29, 2022 at 03:43:37PM +0200, Angel M Alganza wrote: > > > Perhaps if there was a way to configure Mutt to wrap long lines while > > > reading mail with them and Vim to do the same (visually but not > actually > > > including the new lines) while editing they would be bearable for us > who > > > preffer wrapped mail? > > > > You can do that. For mutt: > > > > unset markers > > set wrap = 78 > > > > That'll wrap long lines at 78 characters and won't use markers to show > where > > a line was wrapped (I found that quite distracting.) > > > > For vim, you can enable soft line wrapping. For example: > > https://vim.works/2019/03/16/wrapping-text-in-vim/ > > > > I think this is what you mean in your message, at least. This won't wrap > any > > text lines and will leave the client to deal with it as it sees fit. On > > mutt's side, it'll wrap long lines at the 78 char mark. > > > > Cheers, > > > > -- > > José María (Chema) Mateos || https://rinzewind.org > > -- > Marcelo >
Re: Is linewrap dead?
Hi José Maria, I am doing a test. In this message, I seted in vimrc this lines: set wrap set linebreak Here, I will post a lot off words to test. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Marcelo On 29/08/22 at 09:59, José María Mateos wrote: > On Mon, Aug 29, 2022 at 03:43:37PM +0200, Angel M Alganza wrote: > > Perhaps if there was a way to configure Mutt to wrap long lines while > > reading mail with them and Vim to do the same (visually but not actually > > including the new lines) while editing they would be bearable for us who > > preffer wrapped mail? > > You can do that. For mutt: > > unset markers > set wrap = 78 > > That'll wrap long lines at 78 characters and won't use markers to show where > a line was wrapped (I found that quite distracting.) > > For vim, you can enable soft line wrapping. For example: > https://vim.works/2019/03/16/wrapping-text-in-vim/ > > I think this is what you mean in your message, at least. This won't wrap any > text lines and will leave the client to deal with it as it sees fit. On > mutt's side, it'll wrap long lines at the 78 char mark. > > Cheers, > > -- > José María (Chema) Mateos || https://rinzewind.org -- Marcelo
Re: Is linewrap dead?
On 2022/09/01 09:31, Mark H. Wood wrote: From my POV, when someone uses one of those MUAs that think a paragraph and a line are the same thing, that person's emails make more work for me, and I find the person annoying. "More work" means, for example, that if I try to quote such a "paragraph", and I touch it at all, emacs re-wraps it without inserting the necessary additional quotation brokets and I have to add them by hand. There's probably a way to fix that, but I can't be bothered to rotate, I mean, adjust it. Sounds like you have auto-fill-mode on. You might want to turn that off for those long-line messages. Or, you could make Emacs fill those quotes correctly by using the command C-x . (set-fill-prefix). You might want to read the manual section about filling text, and not only for those long-line messages. Emacs only semi-automates filling text, which I think is kind of clunky, but it has uses.
Re: trouble with my_hdr and $format_flowed
On Wed, Aug 31, 2022 at 06:45:08PM -0700, Kevin J. McCarthy wrote: In my testing, a header 'Content-Type: text/plain; format=flowed' in the draft file does result in the sent email being format=flowed. My example wasn't great: you *should* add a charset parameter set to your system charset (I'm assuming that's utf-8). For replies, Mutt generated the quoted contents of the reply in your $charset, and it uses the charset parameter when reading in the draft file. If it's unset, Mutt will use $assumed_charset or ascii - which would likely result in '?' characters for non-ascii characters in the reply. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Is linewrap dead?
On Wed, Aug 31, 2022 at 06:35:15PM -0500, Derek Martin wrote: > On Wed, Aug 31, 2022 at 04:38:11PM -0400, John Hawkinson wrote: > > (b) Even if recipients *do* rotate, they will still have the > > subconscious/psychological result that "Dealing with Derek's emails > > takes more work, he is annoying." > > That, arguably, would be my problem, but in 33 years of using e-mail, > has never been. Not once. Not because of the way I format e-mail, at > any rate... =8^) This does happen, but I beg to point out that it happens *both* ways. From my POV, when someone uses one of those MUAs that think a paragraph and a line are the same thing, that person's emails make more work for me, and I find the person annoying. "More work" means, for example, that if I try to quote such a "paragraph", and I touch it at all, emacs re-wraps it without inserting the necessary additional quotation brokets and I have to add them by hand. There's probably a way to fix that, but I can't be bothered to rotate, I mean, adjust it. So this sword really does cut both ways. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
Re: Is linewrap dead?
On Wed, Aug 31, 2022 at 02:48:55PM -0500, Derek Martin wrote: > On Wed, Aug 31, 2022 at 01:46:49PM -0400, John Hawkinson wrote: > > As for standards-compliance, that's a red herring. Long lines are > > not going to trip up any modern client, they're just not. > > It may be less relevant today, but it's still relevant. While the > original reason for the standard was that the myriad of clients would > display long lines improperly or not at all, these days it's not > really about clients. Sendmail truncates lines at 998 characters. It > is not alone. > > [It's conceivable this has become untrue since last I checked, but I > doubt it, and assuming so is not wise. Besides which, I'd be shocked > to discover that all internet sites are on the most modern versions of > their MTAs. It just doesn't happen.] Indeed, it is the MTAs, not the MUAs, that will balk at looong lines. Exim OOTB (at least, on Gentoo) is configured to be quite unforgiving about it. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
Re: Is linewrap dead?
On Thu, Sep 01, 2022 at 08:20:21AM +0200, Angel M Alganza wrote: > 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 some people who will insist on doing that. > > So, is there a way to instruct Mutt to wrap received mail with long > lines to wrap them for me at a sane length so that I don't have to suffer > those ridiculous long lines? I have this in ~/.muttrc: set markers = no set wrap = -5 which wraps lines at 5 columns in from the right. You can also use a positive number to specify an absolute amount. Turning markers off means that wrapped lines won't start with a "+" character. HAving the + there might be preferable. I remove them so I can copy and paste multi-line wrapped URLs into another window to be opened locally (the email is read remotely via ssh to a vm). So maybe try something like: set wrap = 72 set smart_wrap There are other muttrc variables to look into: e.g. smart_wrap That looks good. I might add that. It wraps at word boundaries. > Of course I can reduce the with of the frame on Notion (my window > manager) where I run Mutt to force the wrapping, but I'd rather keep the > size I use for everything else and have Mutt wrapping the text for me. > > Cheers. > Ángel cheers, raf
Re: Is linewrap dead?
First, I'd like to thank Tavis for starting this discussion. I am very pleased to see I am not the only one struggling with this. On 29Aug22 13:28-0400, Logan Rathbone wrote: > FWIW, the solution/compromise I ended up using was to compose > multipart/alternative mails with mutt, sending a very simple HTML mail > and a standard hard-wrapped text-based mail as well. So mobile > mailreaders can read it perfectly, and desktop users can read the > plaintext version correctly as well. > > Believe it or not, mutt actually has very sophisticated functionality to > achieve this, and even comes with a sample script called markdown2html > to assist with this. I tend to write plaintext mails using a subset of > markdown *anyway*, so it works out very well. > > And since sending such mails would obviously annoy certain people (eg, > the users of this ML!) I have mutt set up to prompt if I want to send as > multipart/alternative defaulting to no, as in: > > set send_multipart_alternative = ask-no Thanks for that pointer! I am what you might say a true believer in text/plain. OTOH, the world is very diverse, and looking only into one direction makes me feel missing other people out there. So I tend to like this multipart approach. -- Bastian
