Fork me on GitHub
#calva
<
2019-12-31
>
renewdoit02:12:02

Hi, as a new clava user on macbook, the default keybinding ctl-alt-c is not so convenient as macbook right side has no ctl key, what if I change it to cmd-alt-c?

smashedtoatoms03:12:50

I use an emacs keybinding and remapped everything to their emacs equivalents and it all still works. If you can find something that doesn't conflict with anything else you're doing, roll with it.

Andy Nortrup06:12:28

Hiyo! Very new to both Calva and Clojure, But I'm confused...I've installed Calva in VS Code and jacked in. But when I perform tasks like Evaluating a file, or running tests, I get a output that it is going to do the thing, but doesn't let me know that anything completed, or test results.

Andy Nortrup06:12:26

To boot, when I go in to REPL and attempt to evaluate anything, it just hangs too. So...I'm not sure how I broke something this fast.

pez09:12:11

@j364 can you share your keybindings? I think a lot of people would be interested.

smashedtoatoms16:12:33

I'm not really sure these will be useful for anyone else, but I use https://marketplace.visualstudio.com/items?itemName=lfs.vscode-emacs-friendly with these settings:

{
    "key": "ctrl+c alt+j",
    "command": "calva.jackIn"
  },
  {
    "key": "ctrl+alt+c ctrl+alt+j",
    "command": "-calva.jackIn"
  },
  {
    "key": "ctrl+c ctrl+t",
    "command": "calva.runNamespaceTests",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c t",
    "command": "-calva.runNamespaceTests",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+shift+t",
    "command": "calva.runAllTests",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c shift+t",
    "command": "-calva.runAllTests",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c t",
    "command": "calva.runTestUnderCursor",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c ctrl+alt+t",
    "command": "-calva.runTestUnderCursor",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+e",
    "command": "calva.evaluateSelection",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c e",
    "command": "-calva.evaluateSelection",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+p",
    "command": "calva.evalCurrentFormInREPLWindow",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c ctrl+alt+e",
    "command": "-calva.evalCurrentFormInREPLWindow",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+r",
    "command": "calva.evaluateSelectionReplace",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c r",
    "command": "-calva.evaluateSelectionReplace",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+k",
    "command": "calva.loadFile",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c enter",
    "command": "-calva.loadFile",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+c ctrl+n",
    "command": "calva.loadNamespace",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+alt+c ctrl+alt+n",
    "command": "-calva.loadNamespace",
    "when": "calva:connected"
  },
  {
    "key": "ctrl+g",
    "command": "calva.clearInlineResults",
    "when": "editorTextFocus && !editorHasMultipleSelections && !editorReadOnly && !hasOtherSuggestions && !parameterHintsVisible && !suggestWidgetVisible && editorLangId == 'clojure'"
  },
  {
    "key": "escape",
    "command": "-calva.clearInlineResults",
    "when": "editorTextFocus && !editorHasMultipleSelections && !editorReadOnly && !hasOtherSuggestions && !parameterHintsVisible && !suggestWidgetVisible && editorLangId == 'clojure'"
  },
  {
    "key": "ctrl+c ctrl+c",
    "command": "calva.copyLastResults"
  },
  {
    "key": "ctrl+alt+c ctrl+c",
    "command": "-calva.copyLastResults"
  },

smashedtoatoms16:12:52

This is a work-in-progress.

pez09:12:31

@andy102, that was fast indeed. πŸ˜ƒ It sounds like something is up with the REPL connection. Can you provide the steps you take from opening the project and on? Also any error messages from the jack-in terminal would be useful.

Andy Nortrup16:12:43

No real error messages is the odd thing:

> Executing task: lein update-in :dependencies conj '[nrepl"0.6.0"]' -- update-in :plugins conj '[cider/cider-nrepl"0.22.4"]' -- update-in '[:repl-options :nrepl-middleware]' conj '["cider.nrepl/cider-middleware"]' -- with-profile +uberjar repl :headless <

OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
nREPL server started on port 49669 on host 127.0.0.1 - 

Andy Nortrup16:12:01

Steps: 1. Jackin 2. "Lein" 3. :uberjar Really just took the defaults.

Andy Nortrup16:12:15

This has previously worked with lein run and lein test , but adding Calva (which I like for a better editing experience) has stopped finding and running tests or really completing any tasks at all.

Andy Nortrup16:12:18

Thanks for the help.

Andy Nortrup16:12:08

False alarm, I think I created an endless loop while trying to figure out how to recurse and hence things were hanging.

Andy Nortrup16:12:12

😞 More to learn

Cam09:12:54

Hey, I installed parinfer, but just reading the calva docs (yeah, should have read them first!) And I see calva has its own paredit .... Should I remove parinfer??

pez10:12:14

@cam.asoftware, you should be able to use both, I think the settings needed for that are documented as well. However, unless you are really hooked on parinfer, it is not needed. Calva sports among the best paredit implementations out there.

Cam10:12:25

Thanks @pez I'm not hooked at all on parinfer, I just had assumed that to ease the entry to lisp I should use it, but really pleased to see calva offers this. Was just reading your vision on calva (very well written btw) and indeed, the built in handling of parens is definitely inline with the vision of keeping the barrier to entry low. I've listened to you on defn podcast, and as a newcomer, I think this is a great feature that is probably worth highlighting a bit more. As a n00b, we don't know of the paredit/parinfer editor enhancements, because we don't know about the parens/formatting of Clojure. One of those, "you don't know what you don't know" scenarios

Cam10:12:10

But now that I have played in the repl, I'm hooked. Here is a feature idea, food for thought: imagine being able to place markers in the gutter at the beginning of one or more forms (like the idea of breakpoints) Then, when the editor saves a file, each form is automatically evaluated (top to bottom) in the repl, or inline (based on user preferences) this would allow Devs to, for example, create a data structure, a function, and a function call. So they would mark all three forms..... Modify to their hearts content.... Save, and bingo, evaluation shows the result(s)

Joni12:12:58

You could just have a function call with your data structure at the end of the ns so it would automatically run on evaluation?

bringe15:12:15

Hey Cam. I'm not sure if you're aware of the Eval on Save setting. You can check this in Calva's settings and your file will be evaluated on save. If you want to pick and choose which things evaluate "at once". You can add them in a comment form in your file and either evaluate each one individually or add them all inside a do form and evaluate the top-level do which will evaluate all forms inside it.

Cam10:12:55

I've been considering an open source contribution, so as long I can write such a thing for calva in cljs, then I'd love to have a go 😁

pez11:12:58

Someone floated an interesting idea the other day, that your suggestion sort of touches. Iirc, it was about Calva keeping track of, and showing, the evaluation status of the top level forms. That way you would see when forms you rely on need to be re-evaluated. Not sure if that was suggested just here or if someone filed an issue about it, but anyway, I think it would take us a long way towards control of the evaluation process.

didibus07:01:28

If I understand you correctly, Cider does that. The gutter shows a green line next to forms that havn't changed since last evaluated.

pez07:01:51

Ah, cool. That sounds very much like how I think about it.

Cam11:12:58

Right! Yes, that makes sense too. For me, it's about keeping shortcut key and cursor movements to a minimum. On a scale of 1-10, how hard would that be to implement do you think @pez?

pez11:12:08

Which one? πŸ˜€

Cam11:12:08

I imagine markers that are always evaluated as a result of some event would be easier. Then there is no need to keep track of existing forms

Cam11:12:49

I think go for the easiest, and see how people like it

pez11:12:02

I think it would be pretty hard to get the ux right for those markers. And they would need to be structural anyway.

Cam11:12:39

In the simplest first cut, perhaps just a marker against a form. Fully fledged, yeah harder for sure

pez11:12:30

So probably more work with the markers. And less general. So I'm leaning towards the idea of keeping track of the eval status on every form in the he file. It can later be amended with that we can mark specific forms.

Cam11:12:29

How would "modified" forms be visualised do you think?

pez11:12:27

We should have a zoom session about it (the implementation), I think. There are quite a few things I haven't documented properly yet.

pez11:12:24

I think it should be visualized a bit like the eval markers today. But maybe just in the gutters.

pez11:12:26

I think there are fresh APIs for this for the mini map, so a glance at that should tell you what's the status.

Cam11:12:12

Hmmmm, or even, when the user evals a form, we identify that a form/var the form depends upon requires eval, and just eval it on their behalf?

pez11:12:21

I'm a bit on the defense with such help. But something that tells you that you are using an old definition, maybe?

pez11:12:56

There are also code lense buttons we can use.

Cam11:12:14

Yeah, I agree..... Or we are enforcing a potential side effect. Good point

pez11:12:43

I'll go afk a while now. I'll be happy to pick it up again when we are both online.

Cam11:12:37

No problem. I might collect the info we have discussed. Create an issue in GH?

pez12:12:59

Yeah, issue would be nice.

pez12:12:44

I can do a short zoom now, if you can, @cam.asoftware

alidlorenzo20:12:52

is there a way to explore my project dependency libraries using vscode/calva

smashedtoatoms22:12:18

Not sure about code/calva. I use clj -Stree

pez20:12:57

Not sure what that means? You should be able to navigate to code that you use.

alidlorenzo20:12:06

like in javascript for example, my node_modules are in my project directory, so can easily reference them whereas in clojure they are in my HOME directory (they all seem to be installed globally?) but was using cursive briefly and saw they load them for me and allow me to see them

pez22:12:49

I’m very interested in what Cursive does here, so if you get the time, please describe it. Here’s what I do in Calva.

smashedtoatoms22:12:30

I get the feeling @UPH6EL9DH isn't talking about code navigation, but wants to know how to actually look at what dependencies are in play. I use clj -Stree if that is what he means.

smashedtoatoms22:12:27

Actually, now that I read this, I think I am totally wrong.

alidlorenzo23:12:37

specific scenario is error pops up in repl about a library i'm using, so since it doesn't look like I can click/open specified code line in repl logs, i was looking for ways to navigate to library myself @pez i'm not too familiar with cursive unfortunately so can't comment; i was just using it to compare experiences. but i wasn't aware you could click on require statements like that, so gif is helpful thanks

pez00:01:26

If you evaluate in the REPL window, and get errors, you can click open the stack trace and the file locations will be links taking you to the those locations in the files.