Fork me on GitHub
#lsp
<
2021-03-31
>
devn03:03:23

awesome! it keeps. getting. better!

anonimitoraf03:03:01

I know right. It seems as if @ericdallo doesn't sleep anymore

😆 1
lread13:03:13

I suspect, to all of our benefit, he might have caught a case of “The Borkdude Effect”.

6
🚀 3
borkdude15:03:33

Don't think too light of this, the #{:lsp :clojure} habit can be a seriously addicting.

simple_smile 3
aw_yeah 1
devn18:03:32

it seems like pretty gratifying work as far as OSS goes (lsp). one of the few things where you get to see the product of your work in all of your existing code without changing any of it.

😃 1
devn18:03:31

also, i’ve really been enjoying saying “check this out…” to coworkers as i get them aboard the lsp train

devn18:03:48

lots of ooooohs and ahhhhs on the incoming and outgoing hierarchies

ericdallo18:03:44

hahahah, glad to hear that 😄

borkdude19:03:25

@ericdallo so how do I see an outgoing call hierarchy? when I type lsp-tree... in emacs, I only see call-hierarchy and when I open that I see incoming hierarchy

ericdallo19:03:03

C-u M-x lsp-treemacs-call-hierarchy

ericdallo19:03:11

it needs the universal argument prefix

borkdude19:03:41

hmm, a bit hard to discover I'd say, but thanks, this works

devn22:04:52

yes, i had the same “oh it’s a treemacs thing” moment

ericdallo22:04:43

We could suggest 2 separated functions for lsp-mode

ericdallo21:03:31

The rename feature is failing on integration tests with that bump though, I'll check that tomorrow