Some Obsidian Syntax Issues

[AgedLace]

I have completed both basic, and advanced, Obsidian syntax testing based upon the Obsidian Help pages.

The first issue I ran into is that since I had already tested Obsidian callouts, I tried to embed that file into my note. While it embedded in Obsidian, it did not do so on the locally generated web page.

Second, All Obsidian comments are rendered on the locally generated web page.

I also ran into an issue with Obsidian's example of nesting an unordered list into an ordered list. I'm certain this must be an Obsidian setting. I turned off "smart indent in lists" and this did not fix my issue. I will have to research this more on my end.

As for the Advanced Obsidian Markdown Syntax, the MathJax examples did not render correctly on the local web page. I don't have the time to research this more at this time. Hopefully, later in the week.

I tried to push my latest changes to the github repo. For some reason, VS Code is telling me I have missing or invalid credentials. This, too, is an issue I have locally and will need more time to research this issue.

I have the build and debug logs, but there were no errors / warnings generated, so I wont attach them here.

Once I am able to figure out why VS Code has stopped authenticating my git credentials, I will upload the repository for your review. I am unable to do this right now. I hope to get to it in the next day or two.

[mkusz]

@AgedLace Can you point me to the sections of the obsidian documentation where are the elements you have mentioned described?

[AgedLace]

Here are the two Obsidian Help Pages ...

Basic Formatting Syntax - This page covers the nested unordered list in an ordered list.

Advanced Formatting Syntax - The very last section on this page deals with MathJax.

Also, my VSCode issue may be due to a recent update. I'm also installing the latest Manjaro update that came in today. Hopefully, VSCode will work again thereafter.

[AgedLace]

VSCode and Manjaro updates fixed my github missing / invalid authentication issue. The Repo is here.

CORRECTION - the initial push to the repo worked and I was able to push it to github, but when I try to push changes, I get the same error again. Going back to researching.

NEW CORRECTION - Managed to fix it. Working now.

[mkusz]

@AgedLace thank you for all the insight. I need to push v1.1.1 with current fixes for wikilinks and then I will create a proper workflow for reporting issues. Afer that we will create a separate issues per each of your finding, so it will be easier to track progess and do a faster release cycle. This will help to organize stuff and help me with some repo statistics in the backstage so the project will get some additional traction and visibility in other places like in awesome MkDocs catalog (project will be added just after this relese). Thanks for all of your work so far. It's very helpful.

PS. Some of your findings are easy to fix (MathJax) and some will need some hard development (like mixing unordered and ordered lists, since it's not supported by any Markdown extension).

[mkusz]

@AgedLace v1.1.1 is released. I hope you don't mind that I mentioned you in the official blog post, since you are very active in this project as a tester and was a very crucial part of this release. In the next few days I will create issues menitoned in my previous message and close this discussion.

[mkusz]

There are a few very useful like:

• Linter - helps a lot with yaml frontmatter
• Templater - the best plugin for templates
• LanguageTool Integration - best grammar/language correction (not only for Obsidian, very usefull for non EN people like me)

There are a few more that I want to integrate (or already integrated) like advanced tables, charts, mindmap and icons. When template repository will be created, Obsidian vault will be part of it (with those plugins).

[AgedLace]

I use both Linter and Templater,. Will check out the Language Tool Integration!

[mkusz]

@AgedLace If you will ever use paid licence for LanguageTool Integration, don't forget to add this line */.obsidian/plugins/obsidian-languagetool-plugin to yours .gitignore. It's need because licence is stored in one of the file from that directory and if you push it to the repo, it will be publically available and anybody can use it. If you ever do it, you need to write to LanguageTool support team to regenerate your licence. Been there, done that 😄

[AgedLace]

Thank you!!! Appreciate that very much.

[mkusz]

Hi @AgedLace
I have added issue templates (need some polishing, but they are functional). Also, I have made a few issues from this discussion:

• Add support for Obsidian.md comment syntax #46
• Add support for Obsidian.md MathJax syntax #49 (take a look at my comment inside the issue)
• Add support for Obsidian.md mix of ordered and unordered lists #48
• Add support for internal links preview #50

[mkusz]

I'm closing this discussion and let's move it to the reported issues.