2014-07-15 00:51:33 +04:00
|
|
|
# http://daringfireball.net/projects/markdown
|
|
|
|
# ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
|
|
|
|
|
|
|
|
# Detection
|
|
|
|
# ‾‾‾‾‾‾‾‾‾
|
|
|
|
|
2015-08-13 22:06:55 +03:00
|
|
|
hook global BufCreate .*[.](markdown|md|mkd) %{
|
2017-11-03 10:34:41 +03:00
|
|
|
set-option buffer filetype markdown
|
2014-07-15 00:51:33 +04:00
|
|
|
}
|
|
|
|
|
2019-04-12 01:54:58 +03:00
|
|
|
# Initialization
|
|
|
|
# ‾‾‾‾‾‾‾‾‾‾‾‾‾‾
|
|
|
|
|
|
|
|
hook global WinSetOption filetype=markdown %{
|
2019-03-13 08:24:33 +03:00
|
|
|
require-module markdown
|
2019-04-12 01:54:58 +03:00
|
|
|
|
|
|
|
hook window InsertChar \n -group markdown-indent markdown-indent-on-new-line
|
|
|
|
hook -once -always window WinSetOption filetype=.* %{ remove-hooks window markdown-.+ }
|
2019-03-13 08:24:33 +03:00
|
|
|
}
|
|
|
|
|
2019-04-12 01:54:58 +03:00
|
|
|
hook -group markdown-highlight global WinSetOption filetype=markdown %{
|
|
|
|
add-highlighter window/markdown ref markdown
|
|
|
|
hook -once -always window WinSetOption filetype=.* %{ remove-highlighter window/markdown }
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2019-03-13 08:24:33 +03:00
|
|
|
provide-module markdown %{
|
|
|
|
|
2014-07-15 00:51:33 +04:00
|
|
|
# Highlighters
|
|
|
|
# ‾‾‾‾‾‾‾‾‾‾‾‾
|
|
|
|
|
2018-06-28 15:10:22 +03:00
|
|
|
add-highlighter shared/markdown regions
|
2018-11-08 20:44:03 +03:00
|
|
|
add-highlighter shared/markdown/inline default-region regions
|
|
|
|
add-highlighter shared/markdown/inline/text default-region group
|
2018-06-28 15:10:22 +03:00
|
|
|
|
2018-05-07 00:29:52 +03:00
|
|
|
evaluate-commands %sh{
|
2017-12-12 12:16:37 +03:00
|
|
|
languages="
|
2019-05-28 01:46:55 +03:00
|
|
|
awk c cabal clojure coffee cpp css cucumber d diff dockerfile fish
|
|
|
|
gas go haml haskell html ini java javascript json julia kak kickstart
|
|
|
|
latex lisp lua makefile markdown moon objc perl pug python ragel
|
|
|
|
ruby rust sass scala scss sh swift toml tupfile typescript yaml sql
|
2017-12-12 12:16:37 +03:00
|
|
|
"
|
|
|
|
for lang in ${languages}; do
|
markdown.kak: Clean up code-block and code-span formatting.
Previously, a code block was anything between triple-backtics, including inline
blocks:
some text ```
not a codeblock, but highlighted as one
``` other text
and even if the closing backticks had the wrong indent:
```
this is a code block containing a triple backtick
```
this is still a code block, but Kakoune thinks otherwise
```
Now we use the -match-capture flag to ensure the start and end fences have
exactly the same indent.
Previously, the generic code-block region was defined first, which meant that
it took priority over all the language-specific highlighters. Now we define
the generic code-block highlighting *after* the others, which fixes #2304.
Previously, code-spans were defined as ordinary inline markup, but in Markdown
ordinary formatting doesn't work inside code-spans. Therefore, they are now
regions unto themselves, defined according to section 6.3 of the CommonMark
spec <https://spec.commonmark.org/0.28/#code-spans>, which addresses a comment
on #2111.
2018-09-18 11:55:24 +03:00
|
|
|
printf 'add-highlighter shared/markdown/%s region -match-capture ^(\h*)```\h*%s\\b ^(\h*)``` regions\n' "${lang}" "${lang}"
|
2018-06-28 15:10:22 +03:00
|
|
|
printf 'add-highlighter shared/markdown/%s/ default-region fill meta\n' "${lang}"
|
2018-07-19 11:32:29 +03:00
|
|
|
[ "${lang}" = kak ] && ref=kakrc || ref="${lang}"
|
2018-07-02 13:59:12 +03:00
|
|
|
printf 'add-highlighter shared/markdown/%s/inner region \A```[^\\n]*\K (?=```) ref %s\n' "${lang}" "${ref}"
|
2017-12-12 12:16:37 +03:00
|
|
|
done
|
|
|
|
}
|
2014-07-15 00:51:33 +04:00
|
|
|
|
markdown.kak: Clean up code-block and code-span formatting.
Previously, a code block was anything between triple-backtics, including inline
blocks:
some text ```
not a codeblock, but highlighted as one
``` other text
and even if the closing backticks had the wrong indent:
```
this is a code block containing a triple backtick
```
this is still a code block, but Kakoune thinks otherwise
```
Now we use the -match-capture flag to ensure the start and end fences have
exactly the same indent.
Previously, the generic code-block region was defined first, which meant that
it took priority over all the language-specific highlighters. Now we define
the generic code-block highlighting *after* the others, which fixes #2304.
Previously, code-spans were defined as ordinary inline markup, but in Markdown
ordinary formatting doesn't work inside code-spans. Therefore, they are now
regions unto themselves, defined according to section 6.3 of the CommonMark
spec <https://spec.commonmark.org/0.28/#code-spans>, which addresses a comment
on #2111.
2018-09-18 11:55:24 +03:00
|
|
|
add-highlighter shared/markdown/codeblock region -match-capture \
|
|
|
|
^(\h*)```\h* \
|
|
|
|
^(\h*)```\h*$ \
|
|
|
|
fill meta
|
2018-11-08 20:44:03 +03:00
|
|
|
|
2018-11-09 19:47:14 +03:00
|
|
|
add-highlighter shared/markdown/listblock region ^\h*[-*]\s ^\h*((?=[-*])|$) regions
|
|
|
|
add-highlighter shared/markdown/listblock/marker region \A [-*]\s fill bullet
|
|
|
|
add-highlighter shared/markdown/listblock/content default-region ref markdown/inline
|
2018-11-08 20:44:03 +03:00
|
|
|
|
|
|
|
add-highlighter shared/markdown/inline/code region -match-capture (`+) (`+) fill mono
|
markdown.kak: Clean up code-block and code-span formatting.
Previously, a code block was anything between triple-backtics, including inline
blocks:
some text ```
not a codeblock, but highlighted as one
``` other text
and even if the closing backticks had the wrong indent:
```
this is a code block containing a triple backtick
```
this is still a code block, but Kakoune thinks otherwise
```
Now we use the -match-capture flag to ensure the start and end fences have
exactly the same indent.
Previously, the generic code-block region was defined first, which meant that
it took priority over all the language-specific highlighters. Now we define
the generic code-block highlighting *after* the others, which fixes #2304.
Previously, code-spans were defined as ordinary inline markup, but in Markdown
ordinary formatting doesn't work inside code-spans. Therefore, they are now
regions unto themselves, defined according to section 6.3 of the CommonMark
spec <https://spec.commonmark.org/0.28/#code-spans>, which addresses a comment
on #2111.
2018-09-18 11:55:24 +03:00
|
|
|
|
2014-07-15 00:51:33 +04:00
|
|
|
# Setext-style header
|
2018-11-08 20:44:03 +03:00
|
|
|
add-highlighter shared/markdown/inline/text/ regex (\A|\n\n)[^\n]+\n={2,}\h*\n\h*$ 0:title
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex (\A|\n\n)[^\n]+\n-{2,}\h*\n\h*$ 0:header
|
2014-07-15 00:51:33 +04:00
|
|
|
|
|
|
|
# Atx-style header
|
2018-11-27 10:22:21 +03:00
|
|
|
add-highlighter shared/markdown/inline/text/ regex ^#[^\n]* 0:header
|
2018-11-08 20:44:03 +03:00
|
|
|
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex (?<!\*)(\*([^\s*]|([^\s*](\n?[^\n*])*[^\s*]))\*)(?!\*) 1:italic
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex (?<!_)(_([^\s_]|([^\s_](\n?[^\n_])*[^\s_]))_)(?!_) 1:italic
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex (?<!\*)(\*\*([^\s*]|([^\s*](\n?[^\n*])*[^\s*]))\*\*)(?!\*) 1:bold
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex (?<!_)(__([^\s_]|([^\s_](\n?[^\n_])*[^\s_]))__)(?!_) 1:bold
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex <(([a-z]+://.*?)|((mailto:)?[\w+-]+@[a-z]+[.][a-z]+))> 0:link
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex ^\[[^\]\n]*\]:\h*([^\n]*) 1:link
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex ^\h*(>\h*)+ 0:comment
|
|
|
|
add-highlighter shared/markdown/inline/text/ regex \H\K\h\h$ 0:PrimarySelection
|
2014-07-15 00:51:33 +04:00
|
|
|
|
|
|
|
# Commands
|
|
|
|
# ‾‾‾‾‾‾‾‾
|
|
|
|
|
2017-11-03 10:34:41 +03:00
|
|
|
define-command -hidden markdown-indent-on-new-line %{
|
2017-11-03 11:09:45 +03:00
|
|
|
evaluate-commands -draft -itersel %{
|
2017-01-11 16:56:48 +03:00
|
|
|
# copy block quote(s), list item prefix and following white spaces
|
2017-11-03 11:09:45 +03:00
|
|
|
try %{ execute-keys -draft k <a-x> s ^\h*\K((>\h*)+([*+-]\h)?|(>\h*)*[*+-]\h)\h* <ret> y gh j P }
|
2014-07-15 00:51:33 +04:00
|
|
|
# preserve previous line indent
|
2017-11-03 11:09:45 +03:00
|
|
|
try %{ execute-keys -draft \; K <a-&> }
|
2015-11-04 12:48:47 +03:00
|
|
|
# remove trailing white spaces
|
2017-11-03 11:09:45 +03:00
|
|
|
try %{ execute-keys -draft -itersel %{ k<a-x> s \h+$ <ret> d } }
|
2014-07-15 00:51:33 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-03-13 08:24:33 +03:00
|
|
|
}
|