From: Michael Strey <mstrey@strey.biz>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Duplicated internal crossreference IDs in org-html-publish-to-html [9.0 (release_9.0-251-gc04501 @ /usr/share/emacs/site-lisp/org/)]
Date: Sun, 13 Nov 2016 18:01:40 +0100 [thread overview]
Message-ID: <87d1hzs497.fsf@strey.biz> (raw)
In-Reply-To: <87inrudkq1.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 11 Nov 2016 17:50:30 +0100")
On Fr, 2016-11-11 at 17:50, Nicolas Goaziou wrote:
[...]
>> I would expect unique IDs instead.
>
> Fixed. Thank you.
Thank you!
Best regards
Michael Strey
--
http://www.strey.biz * https://twitter.com/michaelstrey
prev parent reply other threads:[~2016-11-13 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 9:14 Bug: Duplicated internal crossreference IDs in org-html-publish-to-html [9.0 (release_9.0-251-gc04501 @ /usr/share/emacs/site-lisp/org/)] mstrey
2016-11-11 16:50 ` Nicolas Goaziou
2016-11-13 17:01 ` Michael Strey [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1hzs497.fsf@strey.biz \
--to=mstrey@strey.biz \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).