Hello! I'm getting a weird error Failed to run snippet. (intermediate value)(intermediate value)(intermediate value) is not iterable when I try to run the clerk/show! custom REPL command I set up while having a .md file open; it works perfectly fine for .clj files. I tried both https://github.com/BetterThanTomorrow/calva/issues/2208 configuration and https://clojurians.slack.com/archives/CBE668G4R/p1685135480618959 configuration, as well as tinkering with things on my own, and I can't find a way around it — any advice is appreciated!
For .md files. I was planning only mostly using .clj files for Clerk anyway so it's not that huge of a problem for me. I was mainly just curious why this is is popping up for .md files. Especially since the github issue I linked seems to indicate something like this was already encountered & patched(?)
OK. You actually say “why having a .md file open” in the OP. 😃 I am pretty sure I have had this working, and must have broken it with some change. Please file an issue.
Okay, will do!
This may be a a bug in Calva. You say ut works fine for clj files. But it is not clear when it does not work fine. 😃
The UX of Calva's control+delete seems to be incongruent with plain text editing. Details in the thread.
Back in the day I would compile Linux from scratch, before Arch existed. I'm too old for that now! (Although - Hyprland seems cool, and using Super for most keybindings does avoid some of these problems.) Anyway, I have the doc changes, and walked through https://github.com/BetterThanTomorrow/calva/blob/published/docs/PULL_REQUEST_TEMPLATE/docs.md Still new to github. I'll see if I can raise a PR.
I would be happy to look at this. Note: Linux has several desktop environments (notably KDE and Gnome), which sometimes differ quite a bit. Lots of stuff is common, but Gnome /might/ be different from KDE. IMO looking into Gnome is a good start
Or Omarchy 😃 (But maybe that is Gnome or KDE, I wouldn’t know, because Mac dude). Anyway, great if you look into it! 🙏
1) In the VSCode's textfile editor, ctrl+delete deletes back one word (deleteWordLeft). In Calva ctrl+delete does Kill/Delete Backward to Start of List. I expected it to delete one sexp to the left to be closer to what happens in plain text since it "feels" closer in spirit. 2) In Clojure comments, ctrl+delete seems to try to do Kill/Delete Backward to Start of List, but instead - if it is in a list it deletes all the comments back to the start of list - in a toplevel comment at the end of the comment it does nothing - in a toplevel comment in the middle of a comment it deletes to the beginning of the line All this feels inconsistant, at least for me. Some other areas try to treat bindings in comments similar to the textfile's bindings. I was hoping that ctrl+delete would - if in comments delete one word back (deleteWordLeft) - if in list delete on sexp back I can change this for myself, but is this sort of thing something that would be considered a UX issue?
This is notoriously hard to get consistent. It varies between operation systems. So on Mac ctrl+backspace does nothing special (or the same as backspace alone, afaict). On Mac it is alt+backspace that delete words. And it deletes s-expressions in Calva. VS Code supports binding different keys on different platforms, but that can also cause confusion, and is harder to maintain. (Yet, we do it for some bindings.) We can make Calva not handle ctrl+backspace when in line comments, though, and let the system/VS Code handle that its default way. That makes total sense to me. Issue welcome. > - in a toplevel comment at the end of the comment it does nothing I can’t reproduce this. Or, I don’t understand it.
- in a toplevel comment at the end of the comment it does nothing> > I can’t reproduce this. Or, I don’t understand it. Around the 13 second mark I'm trying to delete the word to the left at the end of a comment. I turned on screencast mode:
Oh, and I noticed in the screencast that it's actually control backspace (my keyboard labels it as delete. (sorry!)
Ah, I read “top level comment” as (comment ….) 😃
English is hard!
I entered https://github.com/BetterThanTomorrow/calva/issues/2912. Hopefully I got it clearer! 🙂
I totally forgot about option+backspace! That make sense now. I saw that there is at least one place where there is a special linux keybinding, would it make sense to add another? Linux might be harder, maybe it would be easier to collect a set of keybindings on a web page https://calva.io/emacs-keybindings/?
It was actually ctrl+alt+backspace I meant. Lol.
If you have the inclination it would be nice with a look at the default keybindings for Linux. And I’m not totally opposed to aligning them better with OS defaults, but would welcome help with doing that work. Especially since I am a Mac user and a bit in the dark with Linux and Windows stuff.