From: Jean Louis <bugs@gnu.support>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: The name attribute is obsolete. Consider putting an id attribute
Date: Sun, 19 Mar 2017 16:12:29 +0300 [thread overview]
Message-ID: <20170319131229.GA19685@protected.rcdrun.com> (raw)
In-Reply-To: <87h92p8lg0.fsf@nicolasgoaziou.fr>
On Sun, Mar 19, 2017 at 02:06:55PM +0100, Nicolas Goaziou wrote:
> Hello,
>
> Jean Louis <bugs@gnu.support> writes:
>
> > Here below is the org file, and if I process it with:
> > emacs tmp/test.org --batch -f org-mode -f org-md-export-to-markdown
> >
> > Then I get the file, where I can see the following line:
> > # What is GNU CLISP?<a id="sec-1" name="sec-1"></a>
>
> I cannot reproduce it. Are you using latest Org? Did you try without
> your personal config?
>
> > And the option org-html-allow-name-attribute-in-anchors is off, and I
> > am not sure if it influences markdown export at all.
>
> It does. Markdown back-end is built on top of HTML back-end (e.g., to
> translate tables).
I am using this Org version: Version: 20170105.1723, and I am using
GNU Emacs from "GNU Emacs 26.0.50.1 (x86_64-unknown-linux-gnu, X
toolkit, Xaw3d scroll bars) of 2016-12-07"
Option org-html-allow-name-attribute-in-anchors is nil.
Even if I run with the -Q, I get same result, and that is without
personal config:
emacs -Q tmp/test.org --batch -f org-mode -f org-md-export-to-markdown
where I can see in test.md, the following line:
# What is GNU CLISP?<a id="sec-1" name="sec-1"></a>
Any clues?
Jean
next prev parent reply other threads:[~2017-03-19 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 13:04 The name attribute is obsolete. Consider putting an id attribute Jean Louis
2017-03-19 9:26 ` Nicolas Goaziou
2017-03-19 11:54 ` Jean Louis
2017-03-19 13:06 ` Nicolas Goaziou
2017-03-19 13:12 ` Jean Louis [this message]
2017-03-19 13:25 ` Nicolas Goaziou
2017-03-19 14:13 ` Jean Louis
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=20170319131229.GA19685@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).