Re: "Forward" in the standard way

Jordan Wilson writes: > I ended up hacking together this very ugly function (more of a > script). I imagine it would have been trivial to implement this > properly, but didn't have the time to look at Gnus' internals. It works > most of the time in the way that I wanted.

Re: "Forward" in the standard way

On 2016-03-13 (Sun) at 20:00 (+), I wrote: > I have been trying to forward HTML email (*makes the sign of the > cross*). > > I want to have Gnus treat the email content "in the standard way", > i.e. have the HTML content inline (not as an attachment), and renderable > by non-Gnus email

Re: "Forward" in the standard way

Elias Mårtenson writes: > I'm brining this up here, because I feel that this functionality should be > part of Gnus. Yes, it sounds very useful. > However, my tool is not suitable for this, due to the fact that it > does the HTML rewriting using an external program. If there

Re: "Forward" in the standard way

Adam writes: > As a matter of principle, I still trim excessive .signatures etc. from > such emails, but I have given up teaching everybody how to use email. There ought to be a name for this, like the eternal september... Best regards, Adam -- "Apparantly I was misinformed."

Re: "Forward" in the standard way

Elias writes: > On 6 April 2016 at 16:46, Adam Sjøgren wrote: >> * reformat an email containing a thread of emails full-bottom-quoted >>into the "correct" format (top quoted) >> >> I guess the latter isn't that useful, but sometimes I reformat threads >> to make them

Re: "Forward" in the standard way

On 6 April 2016 at 16:46, Adam Sjøgren wrote: * elide all "full-bottom-quoted" emails, preferably with a line for >each, togglable, > > or > > * reformat an email containing a thread of emails full-bottom-quoted >into the "correct" format (top quoted) > > I

Re: "Forward" in the standard way

a...@koldfront.dk (Adam Sjøgren) writes: > Elias writes: > >> On 14 March 2016 at 04:44, Adam Sjøgren wrote: > >>> I would guess you have to write an HTML-email if you want an inlined >>> email to be treated as HTML. > >> I wrote an entire package to deal with this issue. It's

Re: "Forward" in the standard way

On Wednesday, 6 Apr 2016 at 10:46, Adam Sjøgren wrote: [...] > In this context, but a slightly different subject: It would be cool if > Gnus could: > > * elide all "full-bottom-quoted" emails, preferably with a line for >each, togglable, > > or > > * reformat an email containing a

Re: "Forward" in the standard way

Elias writes: > On 14 March 2016 at 04:44, Adam Sjøgren wrote: >> I would guess you have to write an HTML-email if you want an inlined >> email to be treated as HTML. > I wrote an entire package to deal with this issue. It's difficult to do it > right, and I'm not even

Re: "Forward" in the standard way

I wrote an entire package to deal with this issue. It's difficult to do it right, and I'm not even claiming my tool is good enough for general use (even though me and several colleagues have used it for years). https://github.com/lokedhs/gnus-outlook-style On 14 March 2016 at 04:44, Adam Sjøgren

Re: "Forward" in the standard way

Jordan writes: > I've been through all of them, 1 and 4 incline the HTML but it's treated > as plain text by the receiving client. Is your own email plain text or HTML in this case? I would guess you have to write an HTML-email if you want an inlined email to be treated as HTML. Best

Re: "Forward" in the standard way

I've been through all of them, 1 and 4 incline the HTML but it's treated as plain text by the receiving client. 2 and 3 create attachments of the old email contents. Regards, Jordan -- Sent from Gnus v5.13, Emacs 25.0.92.1 ___ info-gnus-english

Re: "Forward" in the standard way

Jordan writes: > I want to have Gnus treat the email content "in the standard way", > i.e. have the HTML content inline (not as an attachment), and renderable > by non-Gnus email clients. None of the different ARGs gives what you want? ,[ C-h f gnus-summary-mail-forward RET ] |