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
I noticed currently the inline-footnote after heading string cannot be handled properly.
For example, the following heading will change the filename into Heading This is an inline footnote.md
# Heading ^[This is an inline footnote.]
I personally have a use case where I use # Heading ^toc to dynamically generate a TOC under the first heading. The current behavior of this plugin is either cleanup the ^toc after # Heading, or change the filename into Heading toc.md
But in a more generally case, I think currently this plugin cannot handle the "textual style" of heading, where the style is encoded as a prefix or affix with several characters. For example some users may use "§" or "Ch." before the heading.
I'm proposing this to highlight one situation that prevents adaption. If it's not within the focus of what the plugin try to deliver, please feel free to close this issue.
The text was updated successfully, but these errors were encountered:
Thanks for the great plugin!
I noticed currently the inline-footnote after heading string cannot be handled properly.
For example, the following heading will change the filename into
Heading This is an inline footnote.md
I personally have a use case where I use
# Heading ^toc
to dynamically generate a TOC under the first heading. The current behavior of this plugin is either cleanup the^toc
after# Heading
, or change the filename intoHeading toc.md
But in a more generally case, I think currently this plugin cannot handle the "textual style" of heading, where the style is encoded as a prefix or affix with several characters. For example some users may use "§" or "Ch." before the heading.
I'm proposing this to highlight one situation that prevents adaption. If it's not within the focus of what the plugin try to deliver, please feel free to close this issue.
The text was updated successfully, but these errors were encountered: