This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-21
Channels
- # announcements (1)
- # architecture (1)
- # beginners (125)
- # boot (6)
- # boot-dev (2)
- # calva (69)
- # cider (38)
- # cljs-dev (3)
- # clojure (212)
- # clojure-austin (7)
- # clojure-australia (1)
- # clojure-denver (2)
- # clojure-europe (3)
- # clojure-gamedev (1)
- # clojure-hamburg (8)
- # clojure-italy (10)
- # clojure-nl (31)
- # clojure-russia (3)
- # clojure-uk (57)
- # clojurescript (56)
- # core-async (3)
- # cursive (15)
- # datascript (1)
- # duct (28)
- # emacs (6)
- # events (1)
- # figwheel-main (11)
- # fulcro (22)
- # luminus (59)
- # lumo (2)
- # onyx (4)
- # overtone (1)
- # re-frame (1)
- # reagent (4)
- # remote-jobs (3)
- # rum (2)
- # shadow-cljs (84)
- # spacemacs (7)
- # speculative (5)
- # vim (1)
- # yada (127)
have you folks been able to get any paredit capability in the vs code terminal/repl? Or at least autocompletion of parens?
also, I'm noticing calva paredit slurp forward doesn't work with quotation marks. Not sure if that is just an uncommon thing to need or if I'm missing something.
didn't mean that to be critical or anything. loving how vs code/calva just works. I was already a fan of cider but I keep migrating more and more from emacs to vs code and find cider and the repl connections very intuitive if not more smooth here.
@chase-lambert Pertectly valid observation :) That's a known issue with paredit.js
. I have implemented a version that uses a lexically analysed sequence of tokens to address this, it will hopefully be coming online in a few weeks or so. π
We will also start supporting raise-sexp, and convolute-sexp at that point, although if you know a use for the latter please let me know :)
nice! I'm not even experienced enough to really know about all that. "lexically analysed sequence of tokens" Alright. haha. could these paredit capabilities apply to the terminal/repl? Syntax highlighting? Rebel-readline is really cool
The tl:dr is paredit.js just looks at characters in the source and has no idea if it's in a string or comment or whatever. Emacs paredit knows what every part of the file is, and we will soon, too :)
There's a bunch of work reworking the existing stuff but we should be there within a month or so from where I'm standing
https://repl-interactor.netlify.com/ online demo here, but it is just a dumb readline in there, vscode works in our dev branch, but it is not ready for production quite yet
actually on the topic of paredit slurp, I'd love for it to work more similarly to emacs
Key bindings are crazy but I had to find a suitable subset that browsers support π
Hm. I think I would not allow that particular behaviour though, will test on emacs tomorrow when I am at a computer
I have a programmable keyboard and use "mod-taps" whereby my modifiers are on home-row keys but only trigger after they've been held for like 200 ms
I will ping test repls for vscode in the coming weeks here and @ you in it if you like
it just sometimes sends them using a throttle/burst pattern that doesn't typically come from human typists
We will be using vscode keybindings so if you can get them to work in general, you should be okay once it's good to go
are you familiar with emacs keybindings too? i'm using them in vs code and haven't found any conflicts yet with calva which is great.
It bites me under win/linux since that is 'close tab', unless calva is active in the current buffer. :)
That said after a particularly gruelling emacs session I do find I close all my browser tabs by mistake trying to cut text :)
this is off topic but I haven't found an answer to this in vs code chats, is there a keyboard shortcut to move the cursor from the terminal to editor without closing the terminal?
yeah, i was just directed to this: https://stackoverflow.com/questions/42796887/switch-focus-between-editor-and-integrated-terminal-in-visual-studio-code/43012779#43012779 so that could be a decent solution
i'm worried about keybinding craziness as I already use the emacs keybindings here and also switched out calva's defaults to use that 'alt-v' one. If I keep adding more I'm back to my forever tweaking emacs days.
That SO answer is definitely the right solution btw. Guess those actions don't have a default keybinding
π if I understand your setup correctly you have as many 'bucky bits' (modifiers) as you want :)
Love it. But I have this amazingly expensive cherry that clicks like a firecracker that I love. Bet there is a way to do that at the driver level tho
Yeah prolly. Will take a look. If not I haven't written a driver in ages so I should totally write 3 for different OSs π
I started with the default layout for the keyboard I have (olkb's planck) and just started tweaking from there, thinking about what I wanted
my main goal with the layout I arrived at was to move work off my pinkies and onto my thumbs
some things took a bit of iteration, such as moving enter to a layer, or the position of 0 on my numpad