From: Lars Ingebrigtsen <larsi@corrigan.gnus.org>
To: "Elias Mårtenson" <lokedhs@gmail.com>
Cc: "Adam Sjøgren" <asjo@koldfront.dk>, info-gnus-english@gnu.org
Subject: Re: "Forward" in the standard way
Date: Wed, 11 Apr 2018 00:01:51 +0200 [thread overview]
Message-ID: <87h8oi67qo.fsf@mouse.gnus.org> (raw)
In-Reply-To: <mailman.127.1460173141.7477.info-gnus-english@gnu.org> ("Elias =?utf-8?Q?M=C3=A5rtenson=22's?= message of "Sat, 9 Apr 2016 11:38:57 +0800")
Elias Mårtenson <lokedhs@gmail.com> 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 was an
> Elisp implementation of a parser that supports the
> HTML→DOM→Edit→DOM→HTML workflow, I'd be happy to implement it.
Hm... Well, Emacs can parse HTML, and can mutate the DOM (with dom.el),
and it can print the DOM out again (as HTML), so I basically think Emacs
can do this all now? (I realise I'm replying to a two year old email.
:-))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2018-04-10 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 20:00 Jordan Wilson
2016-03-13 20:31 ` Adam Sjøgren
2016-03-13 20:41 ` Jordan Wilson
2016-03-13 20:44 ` Adam Sjøgren
2016-04-06 8:02 ` Elias Mårtenson
2016-04-06 8:46 ` Adam Sjøgren
2016-04-06 11:04 ` Eric S Fraga
2016-04-06 12:53 ` Rasmus
2016-04-09 3:38 ` Elias Mårtenson
2016-04-09 9:33 ` Adam Sjøgren
2016-04-09 9:37 ` Adam Sjøgren
[not found] ` <mailman.127.1460173141.7477.info-gnus-english@gnu.org>
2018-04-10 22:01 ` Lars Ingebrigtsen [this message]
2018-04-14 11:38 ` Jordan Wilson
2018-04-14 18:00 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8oi67qo.fsf@mouse.gnus.org \
--to=larsi@corrigan.gnus.org \
--cc=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.org \
--cc=lokedhs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).