This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-08
Channels
- # announcements (11)
- # babashka (13)
- # beginners (11)
- # biff (2)
- # calva (17)
- # cider (19)
- # clojure (60)
- # clojure-berlin (1)
- # clojure-dev (20)
- # clojure-europe (48)
- # clojure-nl (1)
- # clojure-norway (98)
- # clojure-spec (7)
- # clojure-uk (5)
- # core-typed (32)
- # cursive (13)
- # datomic (12)
- # dev-tooling (5)
- # emacs (7)
- # figwheel-main (2)
- # graalvm (4)
- # hyperfiddle (4)
- # introduce-yourself (1)
- # malli (14)
- # missionary (32)
- # off-topic (7)
- # overtone (4)
- # pedestal (10)
- # proletarian (4)
- # re-frame (8)
- # releases (11)
- # tools-build (1)
- # tools-deps (4)
- # xtdb (38)
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.415 • Refactor some internal document and selection APIs in preparation for multiple selections, addressing https://github.com/BetterThanTomorrow/calva/issues/610 • https://github.com/BetterThanTomorrow/calva/issues/2415 • https://github.com/BetterThanTomorrow/calva/issues/2428 The first item means that @rayatrahman9 is back att adding multi-cursor Paredit again. This time we will take it in steps. This first step you should not even notice (if you do, please holler!)
Is there a way to limit which logs show in my repl? Some warnings from my project are flooding the window
No. You’d have to configure your logger somehow. We will make things better around how things are logged, but nothing planned around log types so far. Maybe that should be discussed too.
maybe adding something similar to the browser console log levels. And changing the list of log types will take affect for new logs and will not affect old ones
I think those kind of things needs to be on the #nrepl level of things, though. Maybe there is something there already, for all I know.
It would seem like a Hard Problem for Calva (or anything else) to distinguish Java Loggers' writings to System.out from other println's. That problem is better addressed at its source, i.e., in the Logger configuration.
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.416 • Internal textNotation testing system supports multiple selections, addressing https://github.com/BetterThanTomorrow/calva/issues/610 • Add new Calva development utility commands to create textNotations from open The second step in @rayatrahman9’s multi-cursor Paredit initiative. Please have fun with the new diagnostics/utility commands. I’ll write something about those in 🧵 reply.
The new diagnostics commands lets you 1. Take a snapshot of some situation in a document, possibly involving multiple selections/cursors. The contents of the file will be converted to the “text notation” format we use for unit testing the editor. So very good for bug reporting editing issues. 2. Convert a text notation snapshot to a new untitled document with the original text and selections restored.
Here’s an example of me having used the commands for creating a repro for a question I have on @rayatrahman9’s PR for adding Paredit Kill Left. https://github.com/BetterThanTomorrow/calva/pull/2427#issuecomment-1985910937 Now, regardless if Rayat deems this to be a bug or a feature, he can add a unit test with my inputs. Very simple example in this case, but even so!
About the steps in the multi-cursor Paredit work. @rayatrahman9 has prepared a few of them and I have tested already. I will try to release two more steps today. The following steps will be behind a feature flag, but can potentially still mess something up. So the point with having multiple releases is so that we can have releases to fall back on for you users, and in worst case, to roll back to. I hope this should not impact you as a users negatively, but am also aware that I’m taking that risk. Apologies in advance and all that. And I hope you will appreciate the wonders of multi-cursor Paredit that is about to happen! ❤️
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.417
• https://github.com/BetterThanTomorrow/calva/issues/2420.
◦ Enable calva.paredit.multicursor
in your settings to try it out. Addressing https://github.com/BetterThanTomorrow/calva/issues/610
You are reading that right. Here comes Paredit movements with multi-cursor support! It’s sweet. Behind a feature flag for now. Please consider enabling it and help test it. If this makes you feel #C02BJCKN0R4 towards @rayatrahman9 I can tell you that that’s what happening to me too! ❤️
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.418
• https://github.com/BetterThanTomorrow/calva/issues/2421
◦ Enable calva.paredit.multicursor
in your settings to try it out. Addressing https://github.com/BetterThanTomorrow/calva/issues/610
Aaaaand multi-cursor structural selections! I have seldom had this much fun testing updates to an application. 😃 According to my testing this implementation works great. Only found some situation where shrink selection didn’t work (in multi-cursor mode only). Will see if I can figure it out and make a minimal repro.
Exciting and thanks! I’ve been a heavy user of multi-cursor before turning into lisper. I will definitely test this out.
The new diagnostics commands lets you 1. Take a snapshot of some situation in a document, possibly involving multiple selections/cursors. The contents of the file will be converted to the “text notation” format we use for unit testing the editor. So very good for bug reporting editing issues. 2. Convert a text notation snapshot to a new untitled document with the original text and selections restored.
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.419 • https://github.com/BetterThanTomorrow/calva/issues/2388 Now a pause from Paredit updates, and we turn to the extract refactorings provided by clojure-lsp. @max.r.rothman has made them follow up with a rename prompt. Thanks! ❤️ 🙏
OMG! Paredit multicursor is awesome 🎉 I didn't even know that was being considered...