From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27178@debbugs.gnu.org, eefacm@gmail.com, npostavs@users.sourceforge.net
Subject: bug#27178: 26.0.50; libxml-parse-*-region functions ignore discard-comments argument
Date: Sat, 14 Apr 2018 15:11:44 +0200 [thread overview]
Message-ID: <87lgdqj5kf.fsf@mouse.gnus.org> (raw)
In-Reply-To: <83r2ni470z.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Apr 2018 09:49:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Why not update the docs, as Noam suggested last June?
Well, it would be nice if we could just get this to work, and it just
occurred to me that supporting this option shouldn't be that difficult:
We can just pre-treat the XML before parsing it.
That is, if discard-comments is mentioned, we can just go through the
buffer and delete all the comments before we point libxml towards it.
On the other hand, we could deprecate that option (since it's rather
nonsensical the way it is now), and just provide a Lisp convenience
function to delete the comments if you don't want comments? I think
that sounds cleaner and much easier to implement.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-14 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 0:07 bug#27178: 26.0.50; libxml-parse-*-region functions ignore discard-comments argument Sean McAfee
2017-06-10 15:50 ` npostavs
2018-04-13 22:54 ` Lars Ingebrigtsen
2018-04-14 6:49 ` Eli Zaretskii
2018-04-14 13:11 ` Lars Ingebrigtsen [this message]
2018-04-14 13:28 ` Eli Zaretskii
2018-04-14 13:54 ` Lars Ingebrigtsen
2018-04-14 15:00 ` Eli Zaretskii
2018-04-14 15:14 ` Lars Ingebrigtsen
2018-04-14 15:17 ` Noam Postavsky
2018-04-14 15:21 ` Lars Ingebrigtsen
2018-04-14 15:35 ` Eli Zaretskii
2018-04-14 15:43 ` Lars Ingebrigtsen
2018-04-14 16:24 ` Eli Zaretskii
2018-04-14 15:35 ` Noam Postavsky
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgdqj5kf.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=27178@debbugs.gnu.org \
--cc=eefacm@gmail.com \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).