Zettlr: Tags erroneously detected inside fenced code blocks

[bit-hug]

Description

Fenced code blocks may contain the hash symbol but should not contain tags for detection by Zettlr. However, in the example below #0 is detected as a tag.

Reproducing

In any fenced code block, include a single backtick, then later within the same fenced code block include a hash character followed immediately by at least one non-whitespace character.

Expected behaviour

Since a single backtick within a fenced code block needn't be escaped in markdown, Zettlr should consistently ignore the hash within the code block when parsing the file for tags regardless of the preceding backtick.

Platform

• OS and version: macOS version 10.13.6
• Zettlr Version: 1.7.5

Thanks

As I haven't posted here before, I just wanted to say thank you for your efforts developing Zettlr. I very much appreciate the design philosophy evident in all aspects of its implementation.

[boring-cyborg[bot]]

Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources!
You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible.
The ideal bug report for us has two qualities:

1. The bug is always reproducible, at least within a certain context. 2. We know exactly what specifically goes wrong, and there is consensus on
   what should happen instead.

Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply _clarify_ why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead!
But now, have a great day and thank you again!

[nathanlesage]

Cannot reproduce in the 1.8.x-develop branch, so I'm assuming it has been fixed meanwhile. If it occurs in the 1.8.0 stable, please comment here so we can have another look.

[bit-hug]

This bug persists in 1.8.0 stable.

[nathanlesage]

Found the error, I originally did not pay too much attention to the fact that there was an uneven number of backticks in your code block (which made the code extraction fail for the complete block) – I've now adapted the regular expression to remove code from the file so it should work out now.