Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

On Tue, Nov 05, 2019 at 07:30:16PM +0100, Richard Z wrote: > On Tue, Nov 05, 2019 at 09:31:27AM -0500, Mark H. Wood wrote: > > > Anyway, a good place to read up on xterm might be > > https://invisible-island.net/xterm/ > > That version of xterm still gets updates several times a year. xterm > >

Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

On Tue, Nov 05, 2019 at 09:31:27AM -0500, Mark H. Wood wrote: > Anyway, a good place to read up on xterm might be > https://invisible-island.net/xterm/ > That version of xterm still gets updates several times a year. xterm > is neither obsolete nor unsupported, just unloved by some distro.s.

Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

Derek Martin wrote: > Hardly anyone uses xterm these days though AFAICT, and configuring it > properly has become a lost art. In fact, quite a few years ago now, I > filed a bug against xterm in some version of Fedora or even Red Hat, > and Red Hat's support people closed the ticket, complaining

Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

On Mon, Nov 04, 2019 at 08:01:29PM -0600, Derek Martin wrote: > On Fri, Nov 01, 2019 at 12:21:15PM +1300, martin f krafft wrote: [snip] > > but in addition to viewing HTML messages, I (and others who have > > added to this thread) would like a way to reply without losing the > > formatting. > > >

Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

On Fri, Nov 01, 2019 at 12:21:15PM +1300, martin f krafft wrote: > Regarding the following, written by "Derek Martin" on 2019-10-31 at 15:39 Uhr > -0500: > > And FWIW, I *was* discussing (very limited, completely text-based) > > support for HTML messages in Mutt. I want it, have wanted it for a

Re: Creating HTML emails with mutt

* raf [11-03-19 18:23]: > Derek Martin wrote: > > > TBH most of the time, if I really need to see what's in an HTML mail, > > I just bounce it to gmail. But sometimes that doesn't work either due > > to DNS-based spam prevention. > > Forwarding the email as an attachment rather than bouncing

Re: Creating HTML emails with mutt

Derek Martin wrote: > TBH most of the time, if I really need to see what's in an HTML mail, > I just bounce it to gmail. But sometimes that doesn't work either due > to DNS-based spam prevention. Forwarding the email as an attachment rather than bouncing it should solve that. cheers, raf

Re: Creating HTML emails with mutt

On Sun, Nov 03, 2019 at 07:56:34AM -0500, Mark H. Wood wrote: I like that Mutt presents emails simply. It ignores all the fancy to-the-pixel formatting, pointless images, distracting backgrounds, and flashing multicolored nonsense. I find that reading mail with Mutt is more restful than with

Re: Creating HTML emails with mutt

* Mark H. Wood [11-03-19 07:58]: > On Sat, Nov 02, 2019 at 12:31:29PM -0400, Patrice Levesque wrote: > > > > > […] virtually all of the people who use mutt either as their only > > > email client or along with others, chose mutt because of its > > > simplicity. > > > > People who want a simple

Re: Creating HTML emails with mutt

On Sat, Nov 02, 2019 at 12:31:29PM -0400, Patrice Levesque wrote: > > > […] virtually all of the people who use mutt either as their only > > email client or along with others, chose mutt because of its > > simplicity. > > People who want a simple text mail client will use Alpine or similar. >

Re: Creating HTML emails with mutt

Regarding the following, written by "Kurt Hackenberg" on 2019-11-03 at 00:11 Uhr -0400: Mutt runs an external text editor to compose plain text; it could do the same for this -- run some external composition program that would return both HTML and plain text. There is nothing stopping you

Re: Creating HTML emails with mutt

Sorry, I'm coming into this late. Early on, Kevin McCarthy said: Native support for multipart/alternative composition isn't in my todo list. Too bad -- that would be conceptually clean, to generate multipart/alternative as part of composition. Mutt runs an external text editor to compose

Re: Creating HTML emails with mutt

> […] virtually all of the people who use mutt either as their only > email client or along with others, chose mutt because of its > simplicity. People who want a simple text mail client will use Alpine or similar. Mutt's possibly the most “complicated” text MUA. I don't use mutt because of its

Re: Creating HTML emails with mutt

Regarding the following, written by "martin f krafft" on 2019-11-02 at 23:40 Uhr +1300: How does this message fare? I’ve hacked up my script so that it actually keeps the ‘>’ even in the HTML, but uses CSS to hide it. Yeah, so I am not convinced at all, because all the html2text converters

Re: Creating HTML emails with mutt

Regarding the following, written by "Martin Trautmann" on 2019-11-02 at 10:22 Uhr +0100: However, the usage of blockquote within HTML is something where there is not necessarily a proper way of handling this - Thunderbird does not do it properly, as you see above. How does handle html itself

Re: Creating HTML emails with mutt

On 19-11-01 11:37, martin f krafft wrote: > Regarding the following, written by “Stefan Hagen” on 2019-11-01 at > 08:53 Uhr +0100: > > While I was able to just write an email and send it, it is now a > process of carefully “coding” an email, previewing, correcting, > previewing,

Re: Creating HTML emails with mutt

On 2019-11-01, Stefan Hagen wrote: > >> . > > This is interesting - I'm trying this... > > I'm using this MIMEBellish script to transform plaintext mail to > multipart mail with HTML for a few years and it works quite well: >

Re: Creating HTML emails with mutt

Regarding the following, written by "Stefan Hagen" on 2019-11-01 at 08:53 Uhr +0100: While I was able to just write an email and send it, it is now a process of carefully "coding" an email, previewing, correcting, previewing, sending... There's a lot of good things to be said about carefully

Re: Creating HTML emails with mutt

Regarding the following, written by "Kevin J. McCarthy" on 2019-11-01 at 14:45 Uhr +0800: I've merged the branch into master. For those who want to give it a try, please see the documentation under "MIME Multipart/Alternative"

Re: Creating HTML emails with mutt

Kevin J. McCarthy wrote: On Tue, Oct 29, 2019 at 06:28:34PM +0800, Kevin J. McCarthy wrote: I'll be working on this in the 'kevin/multipart-alternative' branch, but just fyi that I force-push to my development branches, and they are usually "work in progress". I've merged the branch into

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 06:28:34PM +0800, Kevin J. McCarthy wrote: I'll be working on this in the 'kevin/multipart-alternative' branch, but just fyi that I force-push to my development branches, and they are usually "work in progress". I've merged the branch into master. For those who want

Re: Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

> Regarding the following, written by "Derek Martin" on 2019-10-31 at 15:39 Uhr > -0500: > > And FWIW, I *was* discussing (very limited, completely text-based) > > support for HTML messages in Mutt. I want it, have wanted it for a long > > time, because all of the available options for dealing

Rendering HTML as Markdown in mutt (was: Creating HTML emails with mutt)

Regarding the following, written by "Derek Martin" on 2019-10-31 at 15:39 Uhr -0500: And FWIW, I *was* discussing (very limited, completely text-based) support for HTML messages in Mutt. I want it, have wanted it for a long time, because all of the available options for dealing with it have

Re: Creating HTML emails with mutt

On Thu, Oct 31, 2019 at 10:20:21AM +, John Long wrote: > On Wed, 30 Oct 2019 15:49:05 -0500 > Derek Martin wrote: > > > On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > > > That doesn't really help. From my point the issue is not only what I > > > have to configure or what can be

Re: Creating HTML emails with mutt

On Thu, Oct 31, 2019 at 11:43:07AM +, John Long wrote: > On Thu, 31 Oct 2019 23:47:38 +1300 > martin f krafft wrote: > > > Regarding the following, written by "John Long" on 2019-10-31 at > > 10:30 Uhr +: > > >1. Commonly done != standard. There are standards for things like > > >MIME,

Re: Creating HTML emails with mutt

On Thu 31 Oct 2019 09:24, martin f krafft put forth the proposition: > Regarding the following, written by "Dave Woodfall" on 2019-10-30 at 11:25 > Uhr +: > > When messages turn up with no plain text part to them at all, or one > > that's completely useless, it's wrong. > > I'd guess we all

Re: Creating HTML emails with mutt

I'm uninterested about this thread now. -- 存在于未知的空间

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 23:47:38 +1300 martin f krafft wrote: > Regarding the following, written by "John Long" on 2019-10-31 at > 10:30 Uhr +: > >1. Commonly done != standard. There are standards for things like > >MIME, POP3, IMAP etc. I'm not aware of ANSI, ISO, IETF standards > >that say

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 23:49:37 +1300 martin f krafft wrote: > Regarding the following, written by "John Long" on 2019-10-31 at > 10:17 Uhr +: > >> The approach Kevin proposed is completely HTML-agnostic and leaves > >> it up to the user to provide an external tool that provides the > >> HTML.

Re: Creating HTML emails with mutt

Regarding the following, written by "John Long" on 2019-10-31 at 10:17 Uhr +: The approach Kevin proposed is completely HTML-agnostic and leaves it up to the user to provide an external tool that provides the HTML. Mutt then just does the required MIME-handling, which is clearly within

Re: Creating HTML emails with mutt

Regarding the following, written by "John Long" on 2019-10-31 at 10:30 Uhr +: 1. Commonly done != standard. There are standards for things like MIME, POP3, IMAP etc. I'm not aware of ANSI, ISO, IETF standards that say that HTML email is a thing. Quoting the HTML RFC from 1995: "The

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 16:29:31 -0500 Derek Martin wrote: > On Wed, Oct 30, 2019 at 11:29:31AM +, John Long wrote: > > > I don’t think this is about right and wrong, and not only because > > > there is no objectivity. multipart/alternative is an accepted > > > standard, and so is HTML. You

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 15:49:05 -0500 Derek Martin wrote: > On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > > That doesn't really help. From my point the issue is not only what I > > have to configure or what can be configured, but also how much code > > is behind doing that. Less code

Re: Creating HTML emails with mutt

On Thu, 31 Oct 2019 09:29:23 +1300 martin f krafft wrote: > Regarding the following, written by “John Long” on 2019-10-30 at > 11:31 Uhr +: > > > > From my point the issue is not only what I have to configure or > > what can be configured, but also how much code is behind doing > > that.

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:29:31AM +, John Long wrote: > > I don’t think this is about right and wrong, and not only because > > there is no objectivity. multipart/alternative is an accepted > > standard, and so is HTML. You might not like how things have > > developed, and neither do I, but

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:31:21AM +, John Long wrote: > That doesn't really help. From my point the issue is not only what I > have to configure or what can be configured, but also how much code is > behind doing that. Less code is easier to manage than more code. I > can't see the benefit of

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 07:04:48PM +, John Long wrote: > > so you cater to people who have no idea, and cannot be bothered. > > Which is probably 99.9% of everybody in corp. offices worldwide. > > Don't get me wrong, I'm not advocating for HTML support in mutt. HTML > has absolutely no place

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tue, Oct 29, 2019 at 07:39:34PM -0400, José María Mateos wrote: To me, the gold standard of "selecting URLs while in text mode to be sent to the browser" is a plugin for irssi ("the mutt of IRC clients", I'd say) called simply url.pl. It tracks which URLs have been posted to all channels

Re: Creating HTML emails with mutt

Regarding the following, written by “John Long” on 2019-10-30 at 11:31 Uhr +: From my point the issue is not only what I have to configure or what can be configured, but also how much code is behind doing that. Less code is easier to manage than more code. I can’t see the benefit of junking

Re: Creating HTML emails with mutt

Regarding the following, written by “Mark H. Wood” on 2019-10-30 at 08:22 Uhr -0400: Even Outlook seems incapable of badly damaging blocks of text, indented blocks of text, emphasis, underscore/italics, or lists. I think this is the perfect reason why mutt needs to learn creating

Re: Creating HTML emails with mutt

Regarding the following, written by “Dave Woodfall” on 2019-10-30 at 11:25 Uhr +: When messages turn up with no plain text part to them at all, or one that’s completely useless, it’s wrong. I’d guess we all agree on that point. We’re currently discussing the creation of

Re: Creating HTML emails with mutt

On 2019-10-30, Derek Martin wrote: > On Tue, Oct 29, 2019 at 10:31:19PM -, Grant Edwards wrote: >> On 2019-10-29, martin f krafft wrote: >> That's true (as I understood the problem, anyway). Fortunately, I >> never needed to send a signed message with an attachment (or just a >> signed

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 10:31:19PM -, Grant Edwards wrote: > On 2019-10-29, martin f krafft wrote: > That's true (as I understood the problem, anyway). Fortunately, I > never needed to send a signed message with an attachment (or just a > signed message, AFAIR). Nobody I know would have the

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > escribió: > > > > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > > > > Perhaps not, but the fact that it keeps coming up here is pretty

Re: Creating HTML emails with mutt

On 2019-10-30, Sean Greenslade wrote: > Of course there's massive selection bias in this list. No question > about that. I just wanted to point out that there definitely are > some younger Mutters out there. Though I tend to fall more on the > grumpy about HTML mails side of this argument, so

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 07:53:30 -0700 Sean Greenslade wrote: > Of course there's massive selection bias in this list. No question > about that. I just wanted to point out that there definitely are some > younger Mutters out there. Though I tend to fall more on the grumpy > about HTML mails side of

Re: Creating HTML emails with mutt

On October 30, 2019 7:41:34 AM PDT, Patrick Shanahan wrote: >* Sean Greenslade [10-30-19 10:37]: >> On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > wrote: >> >* Mark H. Wood [10-30-19 08:26]: >> >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >> >> >I'd love to

Re: Creating HTML emails with mutt

* Patrick Shanahan [10-30-19 10:42]: > * Sean Greenslade [10-30-19 10:37]: > > On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > > wrote: > > >* Mark H. Wood [10-30-19 08:26]: > > >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > > >> >I'd love to see some

Re: Creating HTML emails with mutt

* Sean Greenslade [10-30-19 10:37]: > On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan > wrote: > >* Mark H. Wood [10-30-19 08:26]: > >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > >> >I'd love to see some statistics about the age of mutt users. > >> > >> 62 > >

Re: Creating HTML emails with mutt

On October 30, 2019 5:29:01 AM PDT, Patrick Shanahan wrote: >* Mark H. Wood [10-30-19 08:26]: >> On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >> >I'd love to see some statistics about the age of mutt users. >> >> 62 > >78 Not sure if these are guesses at the average or

Re: Creating HTML emails with mutt

* Mark H. Wood [10-30-19 08:26]: > On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: > >I'd love to see some statistics about the age of mutt users. > > 62 78 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 11:37:43PM +1300, martin f krafft wrote: >I'd love to see some statistics about the age of mutt users. 62 -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202

Re: Creating HTML emails with mutt

On Wed, Oct 30, 2019 at 12:57:59PM +1300, martin f krafft wrote: >Regarding the following, written by "Martin Trautmann" on 2019-10-30 at >00:14 Uhr +0100: > > That's such a strange thing. > [...] > since they never learned, how proper threading and quoting could >

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 23:37:43 +1300 martin f krafft wrote: > Regarding the following, written by “Nuno Silva” on 2019-10-30 at > 09:21 Uhr +: > > > > There are users who don’t need text/html. It’s okay to want some > > way to use HTML for e-mail in mutt, but I’d say it’s not okay to > > say

Re: Creating HTML emails with mutt

On Wed 30 Oct 2019 23:53, martin f krafft put forth the proposition: > Regarding the following, written by "Dave Woodfall" on 2019-10-30 at 10:05 > Uhr +: > > I don't think embracing wrong email practices is the way forward. > > I don't think this is about right and wrong, and not only

Re: Creating HTML emails with mutt

On Wed, 30 Oct 2019 23:53:40 +1300 martin f krafft wrote: > Regarding the following, written by “Dave Woodfall” on 2019-10-30 at > 10:05 Uhr +: > > > > I don’t think embracing wrong email practices is the way forward. > > I don’t think this is about right and wrong, and not only because >

Re: Creating HTML emails with mutt

Regarding the following, written by “Dave Woodfall” on 2019-10-30 at 10:05 Uhr +: I don’t think embracing wrong email practices is the way forward. I don’t think this is about right and wrong, and not only because there is no objectivity. multipart/alternative is an accepted standard, and

Re: Creating HTML emails with mutt

Regarding the following, written by “Nuno Silva” on 2019-10-30 at 09:21 Uhr +: There are users who don’t need text/html. It’s okay to want some way to use HTML for e-mail in mutt, but I’d say it’s not okay to say everybody needs it. I’d love to see some statistics about the age of mutt

Re: Creating HTML emails with mutt

On Wed 30 Oct 2019 12:57, martin f krafft put forth the proposition: > Regarding the following, written by "Martin Trautmann" on 2019-10-30 at 00:14 > Uhr +0100: > > That's such a strange thing. > > […] > > since they never learned, how proper threading and quoting could have > > worked? > > 78

Re: Creating HTML emails with mutt

On 2019-10-29, martin f krafft wrote: [...] > Society has moved on, and we all risk sounding like grumpy old folks > reminiscing at the times when everyone knew what netiquette was if we > don't embrace the progress that's been happening around us. And > text/html is part of that progress,

Re: Creating HTML emails with mutt

* Grant Edwards [10-29-19 18:27]: > On 2019-10-29, Patrick Shanahan wrote: > > * Grant Edwards [10-29-19 13:10]: > > > >> Muttdown (a "sendmail" filter) which creates mutlipart alternative > >> html/text messages is the only reason I've been able to continue to > >> use mutt for the past 5-6

Re: Creating HTML emails with mutt

Regarding the following, written by “Martin Trautmann” on 2019-10-30 at 00:14 Uhr +0100: That’s such a strange thing. […] since they never learned, how proper threading and quoting could have worked? 78 characters wide text/plain is just not the lowest common denominator anymore. I am not

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tue, Oct 29, 2019 at 01:37:29PM +1300, martin f krafft wrote: Yes, it does. I think Chris' and José's points were more about requiring an external tool to provide functionality which has become so core to everyday email use that mutt could learn to do it. Urlview also obstructs your view

Re: Creating HTML emails with mutt

On 19-10-29 18:09, Grant Edwards wrote: > Muttdown (a "sendmail" filter) which creates mutlipart alternative > html/text messages is the only reason I've been able to continue to > use mutt for the past 5-6 years. About 90% of the people to whom I > send email can't deal with plaintext only. The

Re: Creating HTML emails with mutt

On 2019-10-29, martin f krafft wrote: > [/home/grante/bin/unmime.py: html rendered using w3m] > Regarding the following, written by “Grant Edwards” on 2019-10-29 at 17:09 Uhr > -: > > Muttdown (a “sendmail” filter) which creates mutlipart alternative html/ > text messages is the only

Re: Creating HTML emails with mutt

On 2019-10-29, (Nuno Silva) wrote: > On 2019-10-29, John Long wrote: > >> On Tue, 29 Oct 2019 14:50:05 -0400 >> Patrick Shanahan wrote: >> >>> * Grant Edwards [10-29-19 13:10]: > [...] >>> > Muttdown (a "sendmail" filter) which creates mutlipart alternative >>> > html/text messages is the

Re: Creating HTML emails with mutt

On 2019-10-29, Patrick Shanahan wrote: > * Grant Edwards [10-29-19 13:10]: > >> Muttdown (a "sendmail" filter) which creates mutlipart alternative >> html/text messages is the only reason I've been able to continue to >> use mutt for the past 5-6 years. About 90% of the people to whom I >> send

Re: Creating HTML emails with mutt

Regarding the following, written by “Grant Edwards” on 2019-10-29 at 17:09 Uhr -: Muttdown (a “sendmail” filter) which creates mutlipart alternative html/text messages is the only reason I’ve been able to continue to use mutt for the past 5-6 years. Muttdown suffers from the same problems

Re: Creating HTML emails with mutt

On 2019-10-29, John Long wrote: > On Tue, 29 Oct 2019 14:50:05 -0400 > Patrick Shanahan wrote: > >> * Grant Edwards [10-29-19 13:10]: [...] >> > Muttdown (a "sendmail" filter) which creates mutlipart alternative >> > html/text messages is the only reason I've been able to continue to >> > use

Re: Creating HTML emails with mutt

On Tue, 29 Oct 2019 14:50:05 -0400 Patrick Shanahan wrote: > * Grant Edwards [10-29-19 13:10]: > > On 2019-10-28, Matthias Apitz wrote: > > > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek > > > Martin escribió: > > >> > FWIW, I (as a mutt user for 15++ years) do not need

Re: Creating HTML emails with mutt

* Grant Edwards [10-29-19 13:10]: > On 2019-10-28, Matthias Apitz wrote: > > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > > escribió: > > > >> > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > >> > >> Perhaps not, but the fact that it keeps coming

Re: Creating HTML emails with mutt

On 2019-10-28, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin > escribió: > >> > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks >> >> Perhaps not, but the fact that it keeps coming up here is pretty clear >> indication that it's

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tue, Oct 29, 2019 at 10:05:10PM +1300, martin f krafft wrote: >Regarding the following, written by "Dave Woodfall" on 2019-10-29 at >08:53 Uhr +: > > I deal with very long links, or long lists of links where the > context is lost, by opening the message in elinks, and

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 10:15:22PM +1300, martin f krafft wrote: Regarding the following, written by "Kevin J. McCarthy" on 2019-10-29 at 12:58 Uhr +0800: instead of the script returning content of a specific type, and thus always with the same content type (unless the filter script is

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tuesday, October 29, 2019 at 13:37:29 +1300, martin f krafft wrote: Regarding the following, written by "Dave Woodfall" on 2019-10-29 at 00:10 Uhr +: >Urlview handles long and short links just fine. I've been >using it for over 10 years. Urlview also obstructs your view to context

Re: Creating HTML emails with mutt

Regarding the following, written by “Kevin J. McCarthy” on 2019-10-29 at 12:58 Uhr +0800: The part creation (and removal) will be in Mutt’s pipeline, and so will follow normal processing that Mutt does. That include encoding, delimiters, charset conversion, etc. So I would like the script to

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

Regarding the following, written by “Dave Woodfall” on 2019-10-29 at 08:53 Uhr +: I deal with very long links, or long lists of links where the context is lost, by opening the message in elinks, and then using elinks’ option to pass a link or current URL to an external application or

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Mon 28 Oct 2019 20:28, Ben Boeckel put forth the proposition: > On Tue, Oct 29, 2019 at 00:10:09 +, Dave Woodfall wrote: > > Urlview handles long and short links just fine. I've been using it > > for over 10 years. > > One issue I have with it is that context is lost. Marketing emails

Re: Creating HTML emails with mutt

On Tue, Oct 29, 2019 at 12:41:44PM +1300, martin f krafft wrote: Script output would be the content-type, a blank line, then the generated content. This makes me itch, but I cannot really devise a better approach. I want to say that the script needs to return the complete MIME part,

Re: Creating HTML emails with mutt

Matthias Apitz writes: > So, run mutt in an unicode-rxvt terminal. It presents URLs underlined > and click-able. I do so and sometimes I do hate it: you click into your Definitely not by default. I'm using rxvt-unicode, and I've tried the "matcher" and "selection" extensions but neither one

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

Regarding the following, written by “雨宫恋叶” on 2019-10-29 at 00:41 Uhr +: For this, I think we should design a pager for that purpose. Urlview could probably be extended accordingly. It’d still be disruptive. Imagine reading a long email, and 75% down you encounter a link you want to

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

October 29, 2019 8:38 AM, "martin f krafft" wrote: > Regarding the following, written by "Dave Woodfall" on 2019-10-29 at 00:10 > Uhr +: > >> Urlview handles long and short links just fine. I've been using it >> for over 10 years. > > Yes, it does. I think Chris' and José's points were

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 06:33:19p. m. -0400, José María Mateos escribió: > On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > >Well, do you speak for you or for a 'lot of people'? Who they are? > >I speak only for my own interests (as I said: I do not need this). > >

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

Regarding the following, written by "Dave Woodfall" on 2019-10-29 at 00:10 Uhr +: Urlview handles long and short links just fine. I've been using it for over 10 years. Yes, it does. I think Chris' and José's points were more about requiring an external tool to provide functionality

Re: Creating HTML emails with mutt

El día martes, octubre 29, 2019 a las 11:19:43a. m. +1300, martin f krafft escribió: > Regarding the following, written by "Matthias Apitz" on 2019-10-28 at 23:11 > Uhr +0100: > >Well, do you speak for you or for a 'lot of people'? Who they are? > >I speak only for my own interests (as I said:

Re: Creating HTML emails with mutt

> 2. The ability to natively display a subset of HTML (the same subset) >with the ability to trigger links to open in a browser (or perhaps >execute an arbitrary configured command). Modern terminal windows >can handle all of the formatting required to do just this much... elinks

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tue, Oct 29, 2019 at 00:10:09 +, Dave Woodfall wrote: > Urlview handles long and short links just fine. I've been using it > for over 10 years. One issue I have with it is that context is lost. Marketing emails today tend to be massive strings with embedded IDs in them. Telling one from

Re: Opening URLs from mutt (was: Creating HTML emails with mutt)

On Tue 29 Oct 2019 12:04, martin f krafft put forth the proposition: > Regarding the following, written by "Chris Green" on 2019-10-28 at 22:40 Uhr > +: > > Isn't that handled by your terminal program? Mine certainly allows > > one to right click on any URL to open it. > > rxvt-unicode also

Re: Creating HTML emails with mutt

Hi Kevin, Thanks for sharing your thoughts and plans on this. This all reads really well, and I think it would go most of the way towards the ideal solution. I have a couple of points/questions about some of the things you propose: If there were an error sending, the alternative would be

Opening URLs from mutt (was: Creating HTML emails with mutt)

Regarding the following, written by "Chris Green" on 2019-10-28 at 22:40 Uhr +: Isn't that handled by your terminal program? Mine certainly allows one to right click on any URL to open it. rxvt-unicode also has an extension ("matcher") that allows you to select and open URLs using the

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 10:40:16PM +, Chris Green wrote: Isn't that handled by your terminal program? Mine certainly allows one to right click on any URL to open it. Not if the URL spans several lines. I think it's a common issue across several terminal programs and last time I read

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 06:33:19PM -0400, José María Mateos wrote: > On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: > > Well, do you speak for you or for a 'lot of people'? Who they are? > > I speak only for my own interests (as I said: I do not need this). > > Talking for

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 11:11:31PM +0100, Matthias Apitz wrote: Well, do you speak for you or for a 'lot of people'? Who they are? I speak only for my own interests (as I said: I do not need this). Talking for myself, I really don't need point 1 (composing of HTML messages), but number 2,

Re: Creating HTML emails with mutt

Regarding the following, written by "Matthias Apitz" on 2019-10-28 at 23:11 Uhr +0100: Well, do you speak for you or for a 'lot of people'? Who they are? I speak only for my own interests (as I said: I do not need this). Matthias, any such feature would of course be optional, and probably

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 04:50:40p. m. -0500, Derek Martin escribió: > > FWIW, I (as a mutt user for 15++ years) do not need this. Thanks > > Perhaps not, but the fact that it keeps coming up here is pretty clear > indication that it's a feature that would be useful to a lot of >

Re: Creating HTML emails with mutt

On Mon, Oct 28, 2019 at 10:06:18PM +0100, Matthias Apitz wrote: > El día lunes, octubre 28, 2019 a las 03:59:01p. m. -0500, Derek Martin > escribió: > > > FWIW, my two biggest wishlist items for Mutt are: > > > > 1. the ability to create and send at least simple HTML messages, with > >or

Re: Creating HTML emails with mutt

El día lunes, octubre 28, 2019 a las 03:59:01p. m. -0500, Derek Martin escribió: > FWIW, my two biggest wishlist items for Mutt are: > > 1. the ability to create and send at least simple HTML messages, with >or without multipart alternatives, specifically for basic text >formatting

Re: Creating HTML emails with mutt

On Sun, Oct 27, 2019 at 10:02:38AM +0800, Kevin J. McCarthy wrote: > On Sat, Oct 26, 2019 at 11:16:25AM +1300, martin f krafft wrote: > Native support for multipart/alternative composition isn't in my todo list. > However, I do have a plan to allow external filter generation of the > alternative.

Re: Creating HTML emails with mutt

On Sat, Oct 26, 2019 at 11:16:25AM +1300, martin f krafft wrote: I need to start sending out `text/html` alternative parts to my messages with mutt. Hi martin, Native support for multipart/alternative composition isn't in my todo list. However, I do have a plan to allow external filter

Re: Creating HTML emails with mutt

Regarding the following, written by “Amit Ramon” on 2019-10-26 at 09:03 Uhr +0300: A few years back I developed a simple filter that does, more or less, what you’re looking for. […] https://github.com/amitramon/plainMail2HTML Thanks for the pointer. If messages aren’t PGP/MIME-signed, then

  1   2   >