This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-02
Channels
- # babashka (117)
- # babashka-sci-dev (6)
- # beginners (34)
- # biff (2)
- # calva (7)
- # clj-kondo (27)
- # clojure (6)
- # clojure-dev (8)
- # clojure-europe (41)
- # clojure-israel (1)
- # clojure-nl (1)
- # clojure-norway (2)
- # clojure-uk (1)
- # clojurescript (22)
- # cursive (3)
- # datascript (12)
- # dev-tooling (4)
- # emacs (13)
- # hyperfiddle (60)
- # introduce-yourself (8)
- # joyride (9)
- # lsp (46)
- # malli (3)
- # mranderson (75)
- # off-topic (40)
- # pathom (9)
- # pedestal (4)
- # reagent (11)
- # reitit (18)
- # releases (2)
- # shadow-cljs (81)
- # squint (18)
Folks, a quick brainstorm - supposing you have an API to highlight anything in an editor - how should you like that API to be? Like, both push-based (I want to highlight this) to callback based (this source changed in these/this position, return the new highlight), etc
Things like is the data structure that the callback should receive as parameters, does it sends you additional data to help highlight, how is this highlight format returned, etc
LSP has similar features that respond via server callback to client (Editor), including semantic-tokens
and lens
and it seems to work nicely, there is some custom server callbacks from other LSPs like Dart that does that as well, example https://emacs-lsp.github.io/lsp-dart/#flutter-widget-guides
@ericdallo yes, I'm aware of this, and it's part of what I want to do. What I actually want to make is something that can be even more customizable, so anyone (regardless of LSP support) can add this feature at will - maybe even responding on things like keypresses and cursor positioning