Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FR: Obsidian Comment %% Has Empty Lines Added Around It

See original GitHub issue

I have the following section:

%%
due-date:: [[2022-06-10]]
%%

which gets linted as follows – the result is not expected or wanted:

%%

due-date:: [[2022-06-10]]

%%

It would be great if Linter would respect the comments’ styling.

Thank you for considering.

Issue Analytics

State:
Created a year ago
Comments:11

Top GitHub Comments

1reaction

pjkaufmancommented, Jul 17, 2022

It will jusy tell you what rules ran and in what ordse @AnnaKornfeldSimpson . However that may help. I tend to create a test file and lint that file removing content until I have a small reproducible situation. Then I start turning on and off rules.

1reaction

pjkaufmancommented, Jul 17, 2022

If I were to guess, this is a bug where ignore replaces the comment with a placeholder and that placeholder is not ignored for adding spaces after it. This causes the check for multiline obsidian comments to fail and thus the lines after paragraphs splits the content up by lines. I will try to confirm this. If I do, I would ask that you create a separate bug since this would be slightly different and I don’t want to forget about it.

The assumption above that I made is not correct as to the cause of the issue. Are you using %% anywhere else in the file? That could cause the issue if it were to go unmatched.