This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-14
Channels
- # announcements (8)
- # babashka (37)
- # beginners (4)
- # biff (19)
- # cider (18)
- # clj-kondo (52)
- # clojure (26)
- # clojure-brasil (5)
- # clojure-dev (12)
- # clojure-europe (34)
- # clojure-nl (1)
- # clojure-norway (32)
- # clojure-uk (7)
- # core-logic (1)
- # data-science (5)
- # emacs (14)
- # honeysql (11)
- # hyperfiddle (37)
- # jobs (1)
- # malli (4)
- # off-topic (38)
- # pedestal (7)
- # portal (30)
- # releases (1)
- # remote-jobs (1)
- # tools-build (8)
- # vim (12)
has anyone else seen the
Company: frontend company-pseudo-tooltip-unless-just-one-frontend error "Text is read-only" on command post-command
in cider repls?
my completion in cider repls is breaking because of that, since I think an upgrade I've done a couple of days ago.well it happens also in clojure namespaces not just the cider repl, but not all the times, if I restart Emacs I think it stays fixed for a while
I also use Company and I haven't seen anything like that
"Text is read-only"
suggests that an (insert)
is attempted over the read-only part of the repl, i.e. the prompt.
Do you get the same exact error message in a .clj file buffer?
yeah, but well not now after I restarted
not sure what triggers this annoying behaviour
...Either way, I'd suggest creating an issue against Company, they have recent commits For good measure, you could try going back in time (Git) a few months
I just encountered this and worked around it by pinning company (the package) to melpa-stable instead of the latest git
ah well good to know I'm not the only one
it still hasn't rehappened since I restarted Emacs
which is even more annoying in a way, not sure what triggers it
@U23DRD8FN I'd really appreciate if you could open a GH issue in Company. Its author is very much responsive. I wouldn't feel comfortable opening a bug report for something I haven't experienced myself yet - he appreciates good quality issues :)
Agreed that it is not at all obvious what triggers the errors to start appearing consistently.
If anybody raises an issue in CIDER, please reference this ^. I’m actually not sure if the root problem is in CIDER or company-mode.