This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (53)
- # babashka (46)
- # beginners (103)
- # biff (1)
- # calva (21)
- # cider (7)
- # circleci (12)
- # clj-kondo (7)
- # cljfx (3)
- # cljsrn (9)
- # clojure (25)
- # clojure-europe (21)
- # clojure-nl (1)
- # clojure-uk (21)
- # clojured (1)
- # clojurescript (49)
- # cursive (20)
- # datomic (33)
- # events (3)
- # fulcro (39)
- # graalvm (20)
- # graphql (2)
- # introduce-yourself (1)
- # jobs (14)
- # keechma (3)
- # lsp (34)
- # malli (18)
- # meander (15)
- # off-topic (30)
- # polylith (10)
- # re-frame (21)
- # releases (2)
- # remote-jobs (5)
- # sci (10)
- # shadow-cljs (16)
- # tools-deps (2)
- # vim (6)
Hi, I'm new to Calva and wondering how you all use the Java integration. I have installed the Redhat Java Support plugin. Code completion works, but e.g.
Go to definition does not. Is there something specific to setup in Calva or should I look at the Java plugin for documentation? One thing that is not clear to me is how does e.g. the Java plugin find dependencies etc, since it is obviously not a maven based project.
Sorry for the radio silence, @U0539NJF7. Go to definition should work at least for java “core” stuff, as long as you have the java sources installed. It depends a bit on which Java version you are using. I don’t know how the Java Support plugin interacts with things, but I doubt it is in play for Clojure files.
Thanks, I will take a deeper look to see if sources are installed etc. Does it work for sources of downloaded dependencies as well?
is there a way to make the calva-repl output automatically hide itself when not needed?
after eval it should be shown, but when I continue to work on the source, it could be hidden again... for example, I press alt+enter to see the results, but then move the cursor or type something to continue coding, I wouldnt need it displayed any more. maybe I should look up vscode docs
Maybe consider having it always closed. And hover the eval results instead, when you are curious about more about it?
hmm, good question, I'd like to have that feature as well I'm used to show-hide sidebar (ctrl+b), show-hide terminal (ctrl+`), it would be lovely to have similar "dockable panel with calva-repl editor window", assignable to show/hide shortcut) Since calva-repl is just an "ordinary editor", it's probably a question on vs-code itself, whether is offers such functionality.
perhaps it offers something as "editor bookmarks", "favorites" or some similar functionality that could help ? :thinking_face:
The specific ask here was for something automatic. I imagine it would be something like that the output window shows for a brief time after an evaluation, then it should hide.
Oh, you're right, there was this ask of automatic hiding. Personally I'd be perfectly fine with custom toggle keyboard shortcut, that would always bring up or hide the same file (output.calva-repl) at the same position in vscode, ie. same behavior as sidebar or terminal
The non-automatic way is to have the output window closed. Then after an evaluation use the command for showing the output window (default bound to
ctrl+alt+c o. Then close it, at will. Or, using the hover instead, efter an evaluation use the command for showing the hover,
cmd+k cmd+i on Mac, then
esc to close the hover.
The VS Code API is super limited, and a bit broken, around controlling where file editors should open. But at least Calva makes an attempt to open the window in the same place as it was last closed from.
I never used
ctrl+alt+c o . It does a good job opening the closed repl editor + it swiches focus. But once I press
ctrl+alt+c o,again in that repl editor, it opens some "random" editor to the same editor group. Is there any "contract" or expectation of what should happen in this case?
I wonder whether it would make sense to change the command in that way, that second press
ctrl+alt+c o (ie executed from active repl window) would simply close that repl window?
Perhaps it would deserve its own command ("Calva: TOGGLE visibility of the Current open repl.....").
So the command is Show Output/REPL Window when a source file is active, and Show File for the Current Output/REPL Window Namespace when the ouput window is active. Both are default bound to the same keyboard shortcut. Ideally, in the case where the REPL window is active it would activate the tab where that file is already opened, if it is opened, but: > The VS Code API is super limited, and a bit broken, around controlling where file editors should open.