Clojurians Log v2

Jack-in produces a command line which injects configured versions the nrep tooling, effectively overriding what is configured in deps.edn. There is currently no way to disable this. But you can change the configuration via the setting calva.jackInDependencyVersions. See: https://calva.io/customizing-jack-in-and-connect/#jack-in-dependency-versions

Thanks! Looking forward to being rid of https://github.com/clojure-emacs/cider-nrepl/issues/936 by going to 0.57.0.

Thanks for heads up. We should update the defaults in Calva.

Problem keybindings I noticed (Gnome mapping in parens) transpose - ctrl+alt+t (new terminal) barfSexpBackward - ctrl+shift+alt+left (switch workspace left) backwardDownSexp - ctrl+alt+up (switch workspace up) backwardUpSexp - ctrl+alt+down (switch workspace down) I could find new bindings for these in VSCode, but that made it even harder to remember the keybinding patterns

What I did:

┌──────────────────────────────────────────────────────────────┐
                 │           Forward list nav                                   │
                 │                                                              │
                 │ Forward Up:   Numpad9                                        │
                 │ Forward Down: Numpad3                                        │
                 │ Forward Up Select:   Shift+Numpad9                           │
                 │ Forward Down Select: Shift+Numpad3                           │
 ┌───────────────┼──────────────────────────────────────────────────────────────┼───────────────┐
 │ Backward      │                                                              │ Forward       │
 │ list          │                                                              │ list          │
 |               |                                                              |               | 
 │ Move: Numpad4 |                                                              │ Move: Numpad6 |
 │ Select: Shift+Numpad4                                                        │ Select: Shift+Numpad6
 │ Barf Backward: Shift+Alt+Numpad6                                             │ Slurp Forward: Alt+Numpad6
 | Slurp Backward: Shift+Alt+Numpad4                                            | Barf Forward: Alt+Numpad4 
 └───────────────┼──────────────────────────────────────────────────────────────┼───────────────┘
                 │           Backward list nav                                  │
                 │                                                              │
                 │ Backward Up:   Numpad7                                       │
                 │ Backward Down: Numpad1                                       │
                 │ Backward Up Select:   Shift+Numpad7                          │
                 │ Backward Down Select: Shift+Numpad1                          │
                 └──────────────────────────────────────────────────────────────┘

- movement keys align with direction (eg 7 is backward up and is the left upper key on the keypad) - slurp/barf keys align with cursor movement, shift changes to left part of the structure - holding shift does selection for movement I find this setup easier to memorize, but it does require a 101 key keyboard.

Aside: to make the keypad recognize Shift+NumpadN, I had to go into Gnome Tweaks and turn on "Shift with numeric keypad keys works as in MS Windows", otherwise the shift key changed the keypad to the arrow keys (which had other conflicts) And in comments the calva select is turned off due to the commands when. Because cursorWordEndRightSelect and cursorWordLeftSelect aren't set, the 4 and 6 are actually sent (overwriting your text). Just set Shift+Numpad4, ... for cursorWordLeftSelect... to fix this

I remapped using ; as a chord key for most of those conflicting keys. Just an example "; RightArrow" is Slurp Forward for me. I use #_ and (comment) for most comments so really don't miss the ; key, though I can hit it twice to get an actual semi-colon.

Oh, that's a good idea! It could actually be anything unused too, like the eject key or something. Years of using emacs has made me a little wary of chords in other editors, but there is value in having everything be close to home row.

@pez point_up::skin-tone-2

Thanks! It’s a bit confusing, yes, and we could improve the docs. But the settings to use are actually, the non-qualified keys. The code looks like so:

export enum JackInDependency {
  'nrepl' = 'nrepl',
  'cider-nrepl' = 'cider-nrepl',
  'cider/piggieback' = 'cider/piggieback',
}

const NREPL_VERSION = () => getConfig().jackInDependencyVersions['nrepl'],
  CIDER_NREPL_VERSION = () => getConfig().jackInDependencyVersions['cider-nrepl'],
  PIGGIEBACK_VERSION = () => getConfig().jackInDependencyVersions['cider/piggieback'];

const cliDependencies = () => {
  return {
    'nrepl/nrepl': NREPL_VERSION(),
    'cider/cider-nrepl': CIDER_NREPL_VERSION(),
  };
};

...

So... nrepl and cider-nrepl... but cider/piggieback instead of just piggieback? 🤣

I have no idea why that happened. 😃

Well, piggieback never has had a maven coordinate without namespace. So there’s that. Neither has cider-nrepl, I think, but anyway.