Plugin is wrongly applied to markdown links with `@`as well

[chrisgrieser]

Essentially, the plugins seems to be applied to as soon as there is an @. However, as in the example shown above, the case where I cite someone from Discord (or from Twitter), also has the [@name] syntax. But as opposed to pandoc citations, those are always followed by (link), so this is actually an unequivocal case for the plugin to not consider something a pandoc citation.

And given that many ppl cite someone from Twitter or Discord, this issue should also come up fairly often enough to warrant a general fix for the plugin (as opposed to simply someone fixing it via css snippet)

[mgmeyers]

This is a bit of a challenging scenario @chrisgrieser, and relates to #34. In my vault, I have literature notes named @citekey.md that I link to using [[@citekey]], and I'd like the citation tooltip to show for these. It is possible, however, for users to set obsidian to use markdown links rather than wikilinks, meaning I would instead do [@citekey](/path/to/@citekey.md). I'm not quite sure what the ideal solution would be here. I'll have to think on it a bit.

[chrisgrieser]

Yeah, I am too much of a coward to ever put characters like @ into my file names, but true, I haven't thought of this scenario. Maybe simply add a toggle in the settings, so users toggle it, depending on whether they sue such files or not?

[danieltomasz]

Maybe exclusion mechanism per folder in settings or per file basis via yaml will be a workaround?

[mgmeyers]

There's now an option to disable cite key processing in links. Let me know if you run into any issues with it

[chrisgrieser]

thank you for all the recent improvements to the plugin <3