logseq-automatic-linker icon indicating copy to clipboard operation
logseq-automatic-linker copied to clipboard

Results 57 logseq-automatic-linker issues
Sort by recently updated
recently updated
newest added

Adding words to the `pagesToIgnore` property won't change anything unless logseq is restarted for good. I.e., the automatic linker continues to behave the same way until next restart despite the...

When linking pages that are put in hierarchical relation, the linker stops at the first layer. E.g. if pages `foo` and `foo/bar` exist, `foo/bar` should autolink to `[[foo/bar]]` and not...

The PR handles 2 additional edge cases for code block and inline code detection. It also resolves an **Inefficient regular expression** code scan alert (see screenshot below) detected by [enabling...

I wouldn't want to use automatic linking because it'll generate too many references, but it'd be good to simply highlight potential matches. This would already be a great starting point,...

Hi, I frequently use renderer blocks, for example `{{renderer code_diagram,d2,kroki.diagram.theme=300&kroki.diagram.sketch=1&containerStyle=width: 400px}}` Unfortunately, if Automatic Linker parses the block - it completely wipes out the block and replaces it (with, for...

as the title says. some way of batch processing all pages and all blocks. I just started using this plugin, but I wouldn't like to have to go through every...

I am using logseq on Window 11, and I encounter below issues: - the shortcut "command + shift + L: is not work. alternatively, "ctrl+shift" is work. idk why -...

It took me a minute to realize that this was not a bug, but rather a missing feature that I expected to exist. When I type out a block and...

I have used this plugin for 3 months now, everything good, except that this plugin also links to tags, which, compared with page blocks, are more commonly used words and...