> but I acknowledge that sometimes comparisons aren't always adequate and
> shouldn't be solely relied upon to express a desired feature.
Yes, that was what I was asking, describing a feature as "I want it to work
like Vscode" is unhelpful if the reader doesn't use Vscode or that feature of
I forgot to mention, based on your feedback @elextr , I expanded the
[README.md](https://github.com/andy5995/pinner/blob/trunk/README.md) with
hopefully a better explanation of the goal of the plugin, and added a link to a
demo video.
--
Reply to this email directly or view it on GitHub:
>write the documentation explaining what this plugin is supposed to do, sounds
>like it does something different to what @eht16 understood "pin" to mean, and
>I have always been confused about what it was meant to do.
I'm happy to elaborate an idea or re-frame a goal if I haven't made myself
Normally i report issues to the developer but this developer never responded to
my previous issue about margins not correct (and probably related to this
problem as well)
So i decided to keep using Adwaita for now
--
Reply to this email directly or view it on GitHub:
> these intrinsic variables/methods should be conditional to module imports,
The code doing highlighting is called lexers because they are just that, pure
syntax, no semantics is available, so no knowledge of what is imported. Its
just whats in the lists.
There are some experiments with
@elextr Truth be told a lot of these intrinsic variables/methods should be
conditional to module imports, exactly in order to alleviate pressure from the
lexer/parser. In the fortls language server, we only start parsing for certain
tokens only if the modules are `USE`d. Our serialised data
