public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: internal link page numbers?
Date: Sun, 11 Jun 2017 10:29:25 +0200	[thread overview]
Message-ID: <20170611082925.GB95963@Johns-MBP.home> (raw)
In-Reply-To: <a2cffc92057a6d133075b499b1228378-A+ZCe59fpk2Wd6l5hS35sQ@public.gmane.org>

The shortcut you suggest isn't really in the spirit of
Markdown, which prioritizes source readability over
easy writeability.

+++ Thomas Lord [Jun 09 17 16:14 ]:

>On the other issue, you suggest writing:
>
>[Appendix: The GNU General Public License 3.0]
>
>That's the opposite of what I am wishing for.  Supposing
>a section header like this:
>
>Appendix: Copyright and Licensing Information {#copyright .unnumbered}
>=============================================
>
>I wish I could write a link like this:
>
>    [](#copyright)
>
>And have the text "Appendix: Copyright ... Information" supplied
>automagically.
>
>That way, if I alter the section header, all such links
>to the section stay in sync.
>
>-t


      parent reply	other threads:[~2017-06-11  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07  0:18 Thomas Lord
     [not found] ` <9c1fc336-b56d-433d-a007-1a094326afce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-06-08  9:39   ` John MacFarlane
     [not found]     ` <20170608093907.GD23518-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-06-09 23:14       ` Thomas Lord
     [not found]         ` <a2cffc92057a6d133075b499b1228378-A+ZCe59fpk2Wd6l5hS35sQ@public.gmane.org>
2017-06-11  8:29           ` John MacFarlane [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170611082925.GB95963@Johns-MBP.home \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).