notepad-plus-plus / notepad-plus-plus/notepad-plus-plus
Markdown UDL does not affect strikethrough
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description of the Issue
When using either of the Markdown UDLs (dark or light) and using the strikethrough format like so:
~~strikethrough~~
which comes out in this Github post editor (which supports Markdown) as:
strikethrough
Using it in Notepad++ with either UDL selected has no effect.
Steps to Reproduce the Issue
- Set language to Markdown
- Type the following:

- As can be seen, there is no visual effect added to the strikethrough text.
Expected Behavior
Perhaps a line would be drawn through the text, or at least the color would change, probably to red.
Actual Behavior
There was no effect.
Debug Information
Notepad++ v8.1.8 (64-bit)
Build time : Oct 19 2021 - 16:59:18
Path : C:\Program Files (x86)\Notepad++\notepad++.exe
Command Line :
Admin mode : ON
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows 10 Home (64-bit)
OS Build : 17134.0
Current ANSI codepage : 1252
Plugins : mimeTools.dll NppConverter.dll NppExport.dll
Source: https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax. This document mentions the strikethrough format for markdown.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the dark and light Markdown UDL definitions used by Notepad++; compare their handling of ~~...~~ with the reported GitHub Markdown behavior. Update the relevant UDL configuration so strikethrough is visibly distinguished, then verify it in Notepad++ using the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100