things.el VS link-hint.el

The current state of things is pretty underwhelming and convoluted. In 2018 I designed a system on top of thingatpt that was not married to any parser (can use regexps or use tree-sitter or anything else to build things) or to any editing style (modal vs. non-modal). I'll probably never complete it due to a lack of time/interest, but it still seems to me that what's needed is something like this, a library in the middle that could be used for any package like this. Not sure why no one else seems to see how good thingatpt could be.

things.el: https://github.com/noctuid/things.el

I've planned to use treesitter in things.el for a long time, but another package will likely become useful long before I have time to do this.

I've designed my own text object/motion system that I hope will eventually bring more "useful" composability to any Emacs user that wants it (see things), but right the implementation is buggy and incomplete.

This issue seems to be related: https://github.com/noctuid/link-hint.el/issues/38

If you like link hinting in vimium and tridactyl, you might also be interested in my package link-hint.

If you keep these open, you may try https://github.com/noctuid/link-hint.el. It works with the treemacs windows.

If you want it for all sorts of links found in Emacs buffers try the link-hint package.

I recently went back to default completions for a few weeks (augmented by the link-hint package), but now switched back to using embark-collect-completions. It can be used in several different ways and I'm currently using it very much in the manner of default completions: the completions are not shown by default (but unlike default completion, once they are shown they update automatically).

In general and in non-standard buffers - Open urls, buttons, and other links with link-hint - Select correct word with flyspell-correct and frog-menu

If you don't want to have to move your cursor over to the link, i recommend link-hint https://github.com/noctuid/link-hint.el