From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Jan Synacek" <jsynacek@redhat.com>, tomas@tuxteam.de
Cc: 41320@debbugs.gnu.org
Subject: bug#41320: sxml attributes of some elements are in reverse order
Date: Sat, 16 May 2020 14:30:07 +0200 [thread overview]
Message-ID: <9b28f66d-59cd-4536-83e0-bf6c783079bc@www.fastmail.com> (raw)
In-Reply-To: <CAPsXM8Wi7SHL-mizbiLD52xROK2AzKo_mMEfF3dPMsjVux9Jng@mail.gmail.com>
On Sat, 16 May 2020, at 14:27, Jan Synacek wrote:
> I don't really have a strong opinion. I simply thought that the order
> in XML->SXML should be the same. Otherwise, I don't see how sxml-match
> is actually useful in such a case.
Attributes ordering should not matter in sxml-match, as per the manual: https://www.gnu.org/software/guile/manual/html_node/sxml_002dmatch.html
next prev parent reply other threads:[~2020-05-16 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 10:29 bug#41320: sxml attributes of some elements are in reverse order Jan Synacek
2020-05-16 11:02 ` tomas
2020-05-16 12:27 ` Jan Synacek
2020-05-16 12:30 ` Linus Björnstam [this message]
2020-05-16 12:50 ` Jan Synacek
2020-05-16 14:21 ` tomas
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b28f66d-59cd-4536-83e0-bf6c783079bc@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=41320@debbugs.gnu.org \
--cc=jsynacek@redhat.com \
--cc=tomas@tuxteam.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).