A list of all functions included in this module, together with suggested names for them.

Wikipedia

Link example (English Wikipedia): grey-headed flying fox → https://en.wikipedia.org/wiki/Grey-headed_flying_fox

Link example (Russian Wikipedia, but any language code can be used): Haskell) → https://ru.wikipedia.org/wiki/Haskell

TV Tropes

Link example (trope): so bad, it's good → http://tvtropes.org/pmwiki/pmwiki.php/Main/SoBadItsGood

Link example (series): Elementary) → http://tvtropes.org/pmwiki/pmwiki.php/Series/Elementary

You can give anything as a category instead of “series”, it'll be capitalised but nothing else.

Facebook

Link example: green → https://facebook.com/green

Vkontakte (Вконтакте)

Link example (username): green → https://vk.com/green

Link example (ID):

1337 → https://vk.com/id1337

Google+

Link example (username): SergeyBrin → SergeyBrin

Link example (username with +): +SergeyBrin → +SergeyBrin

Link example (full name – will just be concatenated): Sergey Brin → Sergey Brin

Link example (ID): Sergey Brin → Sergey Brin

Link example (hashtag): #Australia → #Australia

Twitter

Link example (username): kmett → kmett

Link example (username with @): @kmett → @kmett

Link example (hashtag): #haskell → #haskell

Juick

Link example (username): thefish → thefish

Link example (username with @): @thefish → @thefish

Link example (tag): *Haskell → *Haskell

Google

Link example: random query → random query

Duckduckgo

Link example: random query → random query

Yandex (Russian search engine)

Link example: random query → random query

Baidu (Chinese search engine)

Link example: random query → random query

Node.js – NPM

Link example: markdown → markdown

Javascript – Jam

Link example: pagedown → pagedown

Ruby – RubyGems.org

Link example: github-markdown → github-markdown

Python – PyPI

Link example: Markdown → Markdown

Perl – MetaCPAN (by module)

Link example: Text::Markdown → Text::Markdown

Perl – MetaCPAN (by release)

Link example: Text-Markdown → Text-Markdown

Haskell – Hackage

Link example: cmark → cmark

Rust – Cargo

Link example: hoedown → hoedown

Dart – pub

Link example: md_proc → md_proc

Erlang – Hex

Link example: earmark → earmark

R – CRAN

Link example: markdown → markdown

SWI-Prolog – packages

Link example: markdown → markdown

D – DUB

Link example: dmarkdown → dmarkdown

Bash – bpkg

Link example: markdown → markdown

PHP – PEAR

Link example: Text_Wiki_Doku → Text_Wiki_Doku

Github

Link example: aelve/shortcut-links → aelve/shortcut-links

The repository owner can also be given as an option:

shortcut-links) → shortcut-links

Gitlab

Link example: learnyou/lysa → learnyou/lysa

The repository owner can also be given as an option:

lysa) → lysa

Note that links like https://gitlab.com/owner work but are going to be automatically redirected to either https://gitlab.com/u/owner or https://gitlab.com/groups/owner, depending on whether it's a user or a team. So, it's a case when the “links have to look as authentic as possible” principle is violated (but c'mon, this “u” thing looks ugly anyway).

Bitbucket

Link example: bos/text → bos/text

The repository owner can also be given as an option:

text) → text

Android – Google Play (formerly Play Market)

Link example: Opera Mini → Opera Mini

Chocolatey

Link example: Opera → Opera

Braumeister (Homebrew formulas)

Link example: multimarkdown → multimarkdown

Debian – packages

Link example (stable distribution): ghc → ghc

Link example (experimental distribution, but could be any other): ghc) → ghc

Arch Linux – AUR (“user repository”)

Link example: ghc-git → ghc-git

Linux Mint – packages

Link example: ghc → ghc

Fedora – packages

Link example: ghc → ghc

Gentoo – packages

Link example: dev-lang/ghc → dev-lang/ghc

Link example (category as an option): ghc) → ghc

Note that if you don't specify any category, the link would still work – but there are a lot of packages with overlapping names (like “ace”, “csv”, “http”), and such links would lead to search pages listing several packages. So, it's better to include categories.

openSUSE – packages

Link example: ghc → ghc

Emacs – Marmalade

Link example: markdown-mode → markdown-mode

Emacs – MELPA

Link example: markdown-mode → markdown-mode

Emacs – ELPA

Link example: undo-tree → undo-tree

Sublime Text – Package Control

Link example: MarkdownEditing → MarkdownEditing

Atom – packages

Link example: tidy-markdown → tidy-markdown

Atom – themes

Link example: atom-material-ui → atom-material-ui

jEdit – packages

Link example: MarkdownPlugin → MarkdownPlugin

Vim – scripts

Link example (ID): haskell.vim → haskell.vim

Opera – extensions

Link example: Amazon → Amazon

Opera – themes

Link example: Space theme → Space theme

Firefox – Add-ons (extensions, themes)

Link example: [tree-style-tab] → Tree Style Tab

Chrome – Chrome Web Store (extensions, apps, themes)

Link example: [hdokiejnpimakedhajhdlcegeplioahd] → LastPass

GHC (Glasgow Haskell Compiler) extensions

Link example: ViewPatterns → ViewPatterns

RFCs

Link example: RFC 2026 → RFC 2026

Precise format of recognised text: optional “rfc” (case-insensitive), then arbitrary amount of spaces and punctuation (or nothing), then the number. Examples: “RFC 2026”, “RFC-2026”, “rfc2026”, “rfc #2026”, “2026”, “#2026”.

Ecma standards and technical reports

Link example (standard): ECMA-262 → ECMA-262

Link example (technical report): TR/71 → TR/71

Precise format of recognised text for standards: optional “ECMA” (case-insensitive), then arbitrary amount of spaces and punctuation (or nothing), then the number. Examples: “ECMA-262”, “ECMA 262”, “ecma262”, “ECMA 262”.

Format for technical reports is the same, except that “TR” (instead of “ECMA”) is not optional (so, if there's only a number given, it's considered a standard and not a technical report).

CVEs (Common Vulnerabilities and Exposures)

Link example: CVE-2014-10001 → http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-10001

Precise format of recognised text: optional “cve” (case-insensitive), then arbitrary amount of spaces and punctuation (or nothing), then the year, ‘-’, and a number. Examples: “CVE-2014-10001”, “cve 2014-10001”, “2014-10001”.