This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-21
Channels
- # announcements (1)
- # babashka (13)
- # beginners (85)
- # calva (1)
- # chlorine-clover (16)
- # cider (30)
- # clj-kondo (2)
- # clj-on-windows (5)
- # cljdoc (3)
- # cljs-dev (12)
- # cljsrn (19)
- # clojure (88)
- # clojure-europe (39)
- # clojure-nl (7)
- # clojure-sweden (3)
- # clojure-uk (8)
- # clojurescript (35)
- # core-async (3)
- # data-science (2)
- # datomic (17)
- # defnpodcast (3)
- # deps-new (1)
- # editors (18)
- # emacs (4)
- # events (1)
- # expound (1)
- # figwheel-main (8)
- # fulcro (9)
- # graalvm (2)
- # graalvm-mobile (11)
- # helix (44)
- # jobs (7)
- # lsp (95)
- # luminus (9)
- # malli (6)
- # meander (4)
- # membrane (2)
- # missionary (13)
- # off-topic (98)
- # pathom (2)
- # polylith (4)
- # portal (3)
- # re-frame (6)
- # reagent (27)
- # reitit (3)
- # releases (3)
- # remote-jobs (6)
- # rewrite-clj (1)
- # rum (2)
- # sci (3)
- # shadow-cljs (7)
- # sql (66)
- # tools-deps (80)
- # vim (5)
- # xtdb (3)
Do any other people try to run a clean-ns on BuffWritePre
? If so, have you seen a change where it causes Vim to think the buffer is dirty?
It seems new behavior, and am using NeoVim, NeoVim’s LSP, and clojure-lsp, so trying to narrow down scope of plugin updates…
undo doesn’t show any changes, but it seems to mark the buffer as changed/dirty since last save
People using neovim 0.5+ and https://github.com/lewis6991/gitsigns.nvim , if you see neovim crashing in a git repo after recent updates, have a look at https://github.com/lewis6991/gitsigns.nvim/issues/272 Got bitten by it pretty bad now, took a while to figure out that gitsigns was the issue 😓
fixed now 😄