Repository navigation
Releases: FDscend/vscode_markdown_highlight
Releases · FDscend/vscode_markdown_highlight
Release list
v0.0.5
- Restore color autocomplete when a single
=is typed inside an existing highlight. Selecting a color removes the trigger character and recolors the existing highlight without nesting it; single=characters outside highlights still do not trigger highlight suggestions. - Fix editor highlighting disappearing when highlighted text contains a single
=, keeping editor decorations and syntax highlighting consistent with the preview for this case.
v0.0.4
- Fix highlight autocomplete appearing during ordinary typing and interfering with built-in word and snippet suggestions: highlight suggestions now appear only when the cursor is immediately after
==. - Dismiss highlight autocomplete when a space is typed after
==, instead of keeping cached suggestions visible.
v0.0.3
- Add six highlight colors: a color emoji right after the opening
==(e.g.==🔴Important==) renders as<mark data-highlight="red">Important</mark>. The emoji is treated as a color marker only and is not rendered; anywhere else it stays normal text. - Show colored highlights in the editor as well, using the same palette as the preview.
- Add an editor context menu submenu "Highlight Selected Text" with the default color, the six colors, and "Remove Highlight" (this replaces the previous "Wrap Selection with Highlight" item).
- Add quick fixes (lightbulb) inside a highlight: change its color, switch back to the default color, or remove the highlight.
- Add autocomplete: type
==to pick a color, which inserts the marker and places the cursor inside the highlight. Nothing is suggested inside code blocks or inline code. - Rebind
Ctrl + Shift + =to highlighting with the default color; applying it to text inside an existing highlight changes that highlight instead of nesting a new one. - Remove the
highlightsnippet, now superseded by the color autocomplete. - Style hand-written
<mark data-highlight="...">markup via CSS as a fallback. - Fix wrong highlight positions in the editor when an earlier part of the file contains an unmatched backtick (for example a lone backtick in a table cell): inline code is now paired per line by backtick runs of equal length, so
==...==inside inline code is no longer highlighted and the real highlight next to it is no longer skipped. - Recognize fenced code blocks nested in callouts/quotes and fences of four or more backticks, so
==...==inside them is no longer highlighted; an unclosed fence now extends to the end of the file.