From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Will there ever be a standard wiki-link?
Date: Fri, 23 Aug 2019 09:19:32 -0400 [thread overview]
Message-ID: <db2b6987-1e92-1e0a-6b29-d2b7265ab1cf@reagle.org> (raw)
In-Reply-To: <9cbec34f-8bca-429f-8cf9-954dbeeb6a87-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 8/23/19 5:44 AM, mb21 wrote:
> Interesting... can you link to some example docs for those wikis?
I haven't been tracking it carefully, but I'm increasingly seeing references to "wiki style links" (double bracket) in wiki/notebook apps that use markdown.
Github wiki is probably the biggest driver, for example:
https://github.com/reagle/New-Media-Culture/wiki
https://github.com/reagle/New-Media-Culture/wiki/Home/_edit
I think Notational Velocity and its spawn are also influencing folks.
This is the recent example that prompted my email.
https://github.com/darryllawson/sublime-notedown
And I'd like to suggest they follow the [link]() syntax of gitit, but don't know how to suggest they do so...
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/db2b6987-1e92-1e0a-6b29-d2b7265ab1cf%40reagle.org.
next prev parent reply other threads:[~2019-08-23 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 16:08 Joseph Reagle
[not found] ` <e7323376-2751-e4b4-4d74-14c966bb884a-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-23 9:44 ` mb21
[not found] ` <9cbec34f-8bca-429f-8cf9-954dbeeb6a87-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-23 13:19 ` Joseph Reagle [this message]
[not found] ` <db2b6987-1e92-1e0a-6b29-d2b7265ab1cf-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-23 17:14 ` John MacFarlane
[not found] ` <m2lfvjhkia.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-23 18:17 ` Joseph Reagle
[not found] ` <d8b31c74-f60f-23a8-afc7-3cd2a76924c0-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-23 19:17 ` John MacFarlane
[not found] ` <yh480kmufzbsju.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-23 22:02 ` Kolen Cheung
2019-08-29 12:32 ` Joseph Reagle
2019-08-24 10:06 ` BPJ
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=db2b6987-1e92-1e0a-6b29-d2b7265ab1cf@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).