Commit 8792910
Backwards-incompatible strikethrough changes
There are two orthogonal changes here.
1. Recent versions of Vim/Neovim support `strikethrough` text. We can
use that instead of underline for `~~foo~~` in Pandoc Markdown
files.
2. The `x̶` is two unicode codepoints:
- `0x78`, which is ASCII `x`
- `0x0336`, which in UTF-8 is two bytes: `0xCC 0xB6`. It "combining
long stroke overlay" which is a diacritic, modifying the character
immediately before it.
Vim does not do a great job when `cchar` conceals are defined with
complicated Unicode like this. Even though `x̶` renders fine in my
terminal in Vim, when it's used as a conceal character, only the
first byte was getting rendered.
Rather than fix that, and write `x` directly, I've chosen to delete
this and treat it like bold or italic regions. Given the
`strikethrough` change above, it should be easy to completely
conceal the strikethrough markers, like is done for bold italic,
because the strikethrough will disambiguate.
Users who have already added `strikeout` in the conceal blacklist
(see `g:pandoc#syntax#conceal#blacklist`) will continue to have that
preference disabled. Other users will see a change in the concealled
preview (see screenshots).1 parent ea3fc41 commit 8792910
1 file changed
+2
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
41 | 41 | | |
42 | 42 | | |
43 | 43 | | |
44 | | - | |
45 | 44 | | |
46 | 45 | | |
47 | 46 | | |
| |||
60 | 59 | | |
61 | 60 | | |
62 | 61 | | |
63 | | - | |
64 | 62 | | |
65 | 63 | | |
66 | 64 | | |
| |||
393 | 391 | | |
394 | 392 | | |
395 | 393 | | |
396 | | - | |
397 | | - | |
| 394 | + | |
398 | 395 | | |
399 | 396 | | |
400 | 397 | | |
| |||
699 | 696 | | |
700 | 697 | | |
701 | 698 | | |
702 | | - | |
703 | 699 | | |
704 | 700 | | |
705 | 701 | | |
706 | | - | |
| 702 | + | |
707 | 703 | | |
708 | 704 | | |
709 | 705 | | |
| |||
0 commit comments