Re: Formatting HTML content for colour-terminals (was: Rendering HTML as Markdown in mutt)

2019-10-31 Thread martin f krafft
Regarding the following, written by "Kevin J. McCarthy" on 2019-11-01 at 10:12 Uhr +0800: $allow_ansi can enable this, but I recommend reading the option description and thinking very carefully before doing this. Great, I can confirm this works. So then the challenge becomes to filter out

Re: Formatting HTML content for colour-terminals (was: Rendering HTML as Markdown in mutt)

2019-10-31 Thread Kevin J. McCarthy
On Fri, Nov 01, 2019 at 02:24:22PM +1300, martin f krafft wrote: Step 1 to check: can mutt's pager handle terminal control characters for formatting, or is ncurses going to get in the way? $allow_ansi can enable this, but I recommend reading the option description and thinking very carefully

Formatting HTML content for colour-terminals (was: Rendering HTML as Markdown in mutt)

2019-10-31 Thread martin f krafft
Regarding the following, written by "Akkana Peck" on 2019-10-31 at 18:55 Uhr -0600: That sounds like it's all on the viewing side? I can't speak for Derek, 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

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

2019-10-31 Thread Akkana Peck
> 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)

2019-10-31 Thread martin f krafft
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

2019-10-31 Thread Derek Martin
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

2019-10-31 Thread Derek Martin
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

2019-10-31 Thread Dave Woodfall
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

2019-10-31 Thread 雨宫恋叶
I'm uninterested about this thread now. -- 存在于未知的空间

Re: Creating HTML emails with mutt

2019-10-31 Thread John Long
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

2019-10-31 Thread John Long
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

2019-10-31 Thread martin f krafft
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

2019-10-31 Thread martin f krafft
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

2019-10-31 Thread John Long
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

2019-10-31 Thread John Long
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

2019-10-31 Thread John Long
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.