This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-15
Channels
- # announcements (27)
- # architecture (15)
- # aws (2)
- # babashka (5)
- # beginners (77)
- # calva (42)
- # cider (22)
- # clj-kondo (47)
- # cljfx (7)
- # clojure (66)
- # clojure-australia (1)
- # clojure-europe (32)
- # clojure-france (10)
- # clojure-israel (2)
- # clojure-italy (1)
- # clojure-nl (8)
- # clojure-uk (53)
- # clojurescript (29)
- # conjure (28)
- # core-async (2)
- # cursive (26)
- # data-science (1)
- # datascript (11)
- # datomic (33)
- # emacs (4)
- # fulcro (5)
- # girouette (3)
- # helix (1)
- # jobs (2)
- # leiningen (17)
- # luminus (2)
- # malli (15)
- # music (2)
- # off-topic (51)
- # pathom (3)
- # rdf (91)
- # remote-jobs (1)
- # reveal (7)
- # sci (6)
- # shadow-cljs (10)
- # spacemacs (3)
- # sql (23)
- # tools-deps (52)
- # uncomplicate (2)
- # vim (3)
- # xtdb (9)
Hmm, I can't reproduce this with or without vim-repeat :thinking_face: guessing it's something else conflicting.
Is develop
any different for you now? I changed how I'm quoting / escaping things, should be safe in all cases now.
Can't say I observed what Nate saw (probably because I didn't pay attention), but so far, for me, if I do ,eb
, the buffer is not marked modified
I have a feeling it was some vimscript I was concatenating together and evaluating (which included a single quoted string) conflicting with a mapping that included a single quote (thus, closing the string early) and causing weird things to happen. Complete guess and possibly wrong, but I still fixed that string building and escaping so this can't happen. Maybe there's another issue out there, but that was definitely a hole that needed fixing.
@U38J3881W I was using a very old version of vim-repeat. I updated to the latest and the problem went away