From: simenheg@gmail.com (Simen Heggestøyl)
To: Christophe Troestler <Christophe.Troestler@umons.ac.be>
Cc: 34674@debbugs.gnu.org
Subject: bug#34674: 26.1; shr: better list rendering
Date: Wed, 27 Feb 2019 17:26:04 +0100 [thread overview]
Message-ID: <80tvgpjizn.fsf@gmail.com> (raw)
In-Reply-To: <871s3t79nx.fsf@poincare.umons.ac.be> (Christophe Troestler's message of "Wed, 27 Feb 2019 12:28:18 +0100")
Christophe Troestler <Christophe.Troestler@umons.ac.be> writes:
> 1. shr should take into account the “start” parameter in “<ol start="2">”;
It seems that this part just got addressed in master by commit
8282c34f0f2f4ad2c4956fc595518da64a7bef1f.
-- Simen
next prev parent reply other threads:[~2019-02-27 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 11:28 bug#34674: 26.1; shr: better list rendering Christophe Troestler
2019-02-27 16:26 ` Simen Heggestøyl [this message]
2019-02-27 16:27 ` Basil L. Contovounesios
2019-02-28 11:14 ` Christophe Troestler
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=80tvgpjizn.fsf@gmail.com \
--to=simenheg@gmail.com \
--cc=34674@debbugs.gnu.org \
--cc=Christophe.Troestler@umons.ac.be \
/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).