You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Table of contents does not strip # hash symbols correctly when using the heading-related actions in the Paragraph menu. This includes Promote Heading, Demote Heading, and the 6 items to create a heading at various levels.
Can you reproduce the issue?
Steps to reproduce
Create a new document.
Show the Table of Contents in the side bar.
In the new document, create a heading by typing # Heading.
Observe that the ToC shows Heading.
With the cursor on the same line as this heading, select the menu item Paragraph > Demote Heading or use the shortcut Ctrl+Minus.
Alternatively:
Select the menu item Paragraph > Heading 2 or use the shortcut Ctrl+2 and then type Heading.
Expected behavior:
The Table of Contents shows just the text Heading.
Actual behavior:
The Table of Contents shows the text ## Heading, failing to trim the leading hash characters.
Saving the file and viewing it in plaintext editor shows that the underlying content is fine. Closing and reopening it in Mark Text rebuilds the Table of Contents correctly.
Versions
MarkText version: v0.16.3
Operating system: Windows 11 Home 21H2
The text was updated successfully, but these errors were encountered:
Description
Table of contents does not strip
#
hash symbols correctly when using the heading-related actions in the Paragraph menu. This includes Promote Heading, Demote Heading, and the 6 items to create a heading at various levels.Steps to reproduce
# Heading
.Heading
.Alternatively:
Heading
.Expected behavior:
The Table of Contents shows just the text
Heading
.Actual behavior:
The Table of Contents shows the text
## Heading
, failing to trim the leading hash characters.Saving the file and viewing it in plaintext editor shows that the underlying content is fine. Closing and reopening it in Mark Text rebuilds the Table of Contents correctly.
Versions
The text was updated successfully, but these errors were encountered: