Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-03-16

Channels

#calva
<
2022-03-16
>
Yuner Bekir10:03:31

Is there a way to increase the number of lines that can get shown as a result of a function execution in the repl?

Max15:03:03

This is definitely reviving https://clojurians.slack.com/archives/CBE668G4R/p1642803700114400, but I’ve encountered exceptions taking a long time to show up in a non-dockerized repl. It takes about 3 seconds for the exception to show up, and the stack trace is only 16 lines long time spent serializing it isn’t likely to be the cause. I also notice that if the exception was a CompilerException, after an exception is raised, I see an error popup in the bottom right of VSCode that says “n.filter is not a function”. That might be a separate issue though. Even stranger, this slow exception behavior happens on one of my computers, in a fresh project on another computer, exceptions appear almost instantaneously. Maybe this is unrelated, but it looks like throw might not be getting highlighted correctly either? I’d expect it to be the same color as def. Sorry for the word barf, I’m just excited to have finally reproduced the issue

pez15:03:09

You are welcome to file an issue about the delay. At least I don't thnk we have one... The n.filter might be a clue so mention that in the issue, please.

pez15:03:17

The highlighting... What do you get if you inspect with Developer Inspect Tokens and Scopes?

pez15:03:20

Looks like clojure-lsp is not recognizing it as a macro. I vaguely remember this being a known issue. Maybe search a bit in #lsp about it.

Max15:03:43

Didn’t find anything, I’ll post in there about it

🙏 1
Max16:03:32

Should I add onto this issue or file a new one? https://github.com/BetterThanTomorrow/calva/issues/1051

pez16:03:29

If you think it might be the same issue then add on to it. You can also create a new one and link to it as possibly related. We are not too strict around these things. Mostly people make good calls, and we rather have too many reports than too few. 😃

🙏 1
orestis19:03:29

Oh hey I've been seeing the n.filter thing too! When evaluating a whole file which contains errors. I didn't pay much attention to it

bringe03:03:28

I filed an issue about the n.filter issue recently: https://github.com/BetterThanTomorrow/calva/issues/1567. It’s probably a fairly easy fix, I just haven’t gotten to it.

bringe03:03:58

But others are welcome to take a crack at it too, if anyone wants to.