Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This plugin doesn't work well in a compiled note with the Longform plugin #2

Open
Liong1976 opened this issue Sep 12, 2021 · 3 comments

Comments

@Liong1976
Copy link

I was trying to compile three notes with the Longform plugin and the footnote numbers were expected to be put in an order with this plugin but it didn't work.

Here is the snapshot before I used this plugin:
image

Here is after using the plugin:
image

FYI, I am using Windows and Minimal Theme, Obsidian v.0.12.15

Thanks

@charliecm
Copy link
Owner

Unfortunately, this plugin doesn't re-index the markers in place. Rather, it attempts to match markers ([^1]) to their corresponding definitions ([1]: …) and then re-indexes them, which is useful when you're adding a new marker in between other ones (similar to how footnotes are organized in wiki pages).

@chrisgrieser
Copy link

Unfortunately, this plugin doesn't re-index the markers in place. Rather, it attempts to match markers ([^1]) to their corresponding definitions ([1]: …) and then re-indexes them, which is useful when you're adding a new marker in between other ones (similar to how footnotes are organized in wiki pages).

Ah, that makes sense! Nevertheless, I also agree with @Liong1976, that the ability to properly re-index footnotes would be very useful. Especially considering that the problem will become quite common once all the people using the longform plugin finish their projects.

@Liong1976
Copy link
Author

Unfortunately, this plugin doesn't re-index the markers in place. Rather, it attempts to match markers ([^1]) to their corresponding definitions ([1]: …) and then re-indexes them, which is useful when you're adding a new marker in between other ones (similar to how footnotes are organized in wiki pages).

Thanks, @charliecm, for your explanation. I hope there's a solution for this issue as @chrisgrieser said.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants