This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-29
Channels
- # announcements (4)
- # babashka (38)
- # beginners (66)
- # calva (35)
- # cider (3)
- # clj-on-windows (19)
- # cljs-dev (2)
- # clojure (29)
- # clojure-europe (15)
- # clojure-norway (2)
- # clojurescript (43)
- # clr (7)
- # community-development (6)
- # events (3)
- # hoplon (5)
- # lsp (23)
- # malli (7)
- # matrix (9)
- # nbb (53)
- # off-topic (5)
- # overtone (1)
- # practicalli (2)
- # re-frame (6)
- # reagent (17)
- # reitit (11)
- # specter (5)
- # tools-build (7)
- # xtdb (22)
Hah, I’ve just been reminded about the evaluation fringe indicators. They’re obviously useful, but I think I would get more benefit from them if (1) an indicator was used to show code that has been changed without being re-evaluated (rather than code that has been evaluated), and (2) the indicator extended to every line of the form (rather than just the first line). The display would be unobtrusive for evaluated code (no fringe), and would alert you to unevaluated code even when the first line of the form was beyond the top of the window. If there’s any interest: • I can create a ticket. Perhaps two separate options, one to change when the indicator is shown (and I guess change the colour of the indicator, to red perhaps), and another to extend the indicator to highlight the whole form. Perhaps that should be two separate tickets. • I’d be happy to have a go at this myself, but probably not in the immediate future.
There are previous Cider issues on this subject which seem relevant. I agree the current form is subtle, although the subtle approach helps avoid interference with other markers that use the gutter, e.g. git-gutter, etc.. Original issue: https://github.com/clojure-emacs/cider/issues/2748 Follow-on issue (examples of gutter conflicts) https://github.com/clojure-emacs/cider/pull/2924