Fork me on GitHub
#cider
<
2023-11-14
>
andrea.crotti10:11:39

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.

👍 1
andrea.crotti10:11:16

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

vemv10:11:07

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?

andrea.crotti10:11:46

yeah, but well not now after I restarted

andrea.crotti10:11:51

not sure what triggers this annoying behaviour

vemv10:11:40

does it only happen after you tried completions? Or also spontaneously

vemv10:11:06

...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

wikipunk15:11:33

I just encountered this and worked around it by pinning company (the package) to melpa-stable instead of the latest git

andrea.crotti15:11:07

ah well good to know I'm not the only one

andrea.crotti15:11:19

it still hasn't rehappened since I restarted Emacs

andrea.crotti15:11:29

which is even more annoying in a way, not sure what triggers it

vemv16:11:06

@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 :)

cch117:11:54

Agreed that it is not at all obvious what triggers the errors to start appearing consistently.

cch117:11:44

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.

vemv17:11:38

Given: > I just encountered this and worked around it by pinning company (the package) to melpa-stable instead of the latest git It should be Company-side. Thanks much for the detailed report.

cch117:11:10

Saw that (and your comment on GH -thanks). Now looking into pinning….

📌 1
cch120:11:22

Pinning company-mode worked for me too.