Fork me on GitHub
#calva
<
2023-04-10
>
pez10:04:10

Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.350https://github.com/BetterThanTomorrow/calva/issues/2147 Copying the jack-in command line is a good way to get a command line (or the template for a command line) that will start a REPL that will work well with Calva. Until now the command has not included a command for changing the directory to the root of the project for which the REPL is started. This has left room for a hard-to-detect source of error where the REPL seems to start fine, but since it is started from the wrong project configuration, it will not work well.

orestis16:04:19

I will test this to see how does it work with non-bash shells

orestis14:04:49

Works great!

🙏 2
pez14:04:03

It is mostly a bash command line when on Linux or Mac. No idea how e.g. Fish likes it.

orestis14:04:47

It seems fish doesn't enter into it.

orestis14:04:59

If it does, the pushd; stuff; popd works great

pez12:04:53

I’m going to spend some time trying to make Jack-in infinitely 😃 flexible. Here’s the idea: https://github.com/BetterThanTomorrow/calva/issues/2152 It has been floated in this channel before, but I didn’t find it in the issues, so maybe I had forgotten to add. Please comment on the issue (or in this thread if you prefer) so that we’ll get this feature right. And just ask if it is unclear. The TL;DR is Support custom Jack-in command lines to be configured, and provide the command line with ability to tap into things that Calva knows about the Jack-in situation. The example Babashka script there was written by ChatGPT, btw. 😃 https://twitter.com/pappapez/status/1645387542307405825

phill15:04:18

A little while ago, IIRC, you wrote a monograph about Jack-In coping with the distinct and incompatible interface of every build tool. Meanwhile, for my part, at more or less the same time, I mislaid the one-in-a-trillion-trillions combination of project setup, Calva configuration, and VS Code commands to achieve a ClojureScript REPL. It seemed that an idiot-proof "grand unified jack-in" would be a very splendid ideal. And even more splendid if there were either (a) fewer incompatible interfaces than the full transitive matrix of every-build-tool * every CLJS tool, or (b) more modularity of adapters among interfaces, the more efficiently to parcel and share the burdens of interoperability.

pez15:04:03

We took quite a risk when deciding to support the build tools du jour. But it turns out we did it at a time when the dust was enough settled. I guess there could still show up some build tool that solves things in interestingly enough ways to gain traction and seriously challenge the infrastructure we have. But it doesn’t look that way right now. Did you succeed in achieving your REPL using Jack-in, or did you have to retreat back to manual start?

skylize16:04:44

It seems like I've managed to make some comments recently that are getting under the skin of @pez. I'm not totally clear on why, and will not attempt any deep speculation here. (Happy to listen @pez, if you want to dig into it in a private thread.) But to the extent I am able without fully understanding, I would like to apologize for bringing negativity into this channel. In case it matters, I want to publicly make it very clear that I am both highly appreciative and constantly amazed by Calva; and by the work done by @pez, the rest of <!subteam^S03BGSAUPTQ>, and any other contributors for getting Calva where it is today. So for anything I ever say about Calva that comes across in any way negative, please know that it comes from a place of only the best intentions. --- I hope I can encourage everyone here to try and interpret generously; not just for my comments, but for anyone you speak with. Try not to assume that someone is attacking you or your work or anything you care about when there are other ways you could choose to interpret things. Particularly in my case, I know I am extremely open with my thoughts, quite blunt, and usually speak with strong confidence if I choose to speak at all. I know this can come across as brash and insensitive, or condescending. Unfortunately, that is just how my brain works. Through the years, I have made great strides toward being more tactful. But for a large subset of things that anger or annoy or otherwise bother people, I am genuinely only able to grasp it at an intellectual level after the fact. I can analyze what was said after someone gets upset, and use logic to make reasonable guesses at a trigger. With luck, I might learn something from the analysis to predict reactions in some future conversation. But in general I cannot get very far by simply asking myself how "I would feel if ... ?". In lieu of aggressive self censorship (just shut up and stay out of it), my only option is usually to just say my piece and hope I don't step in it. I hope you all can find it in you to put up with my lack of grace, and to interpret my words generously.

❤️ 12
skylize16:04:00

There is a meaningful flip side of my blunt speech: No matter how confident I seem when I say something, I am always fully open to the possibility I am wrong. So don't think you will get under my skin by pointing out any errors. If I still disagree, I will probably argue a bit. Or in some cases, I might correct myself based on raised incongruities. But when presented with valid arguments against claims I have made, I can easily flip on a dime to incorporate an entirely new perspective; and be grateful for the chance to learn something new in the process. So please have at it if you ever think I am spewing disinformation. Rip my comments apart and correct the record.

pez17:04:36

Oh, wow. Thanks for writing this, @U90R0EPHA . I shall admit that yes, some of your comments has managed to get under my skin. But knowing this you have just told us, I will reinterpret all comments. It really is not that I don’t appreciate your engagement. I do! Sometimes you have a tendency to second guess others, or at least to express yourself in a way that I have taken as second guessing. But with me, from now on, I will be much farther from taking things you say like that. I apologize for losing my temper in that other thread yesterday. Thanks again. Let’s continue to work together to make Calva the best we can make it!

1
bringe18:04:19

I also appreciate your engagement in this channel as well as on GitHub. Thanks for taking the time to explain your above thoughts.

☺️ 1
wevrem19:04:59

This exchange right here is a good example of why the Clojure community is such a good place. Thank you all for leading out with courage and kindness.

❤️ 5
skylize20:04:28

Another extension on what I said above is that I have a strong attraction to debate as a method of learning and self-correction. By presenting my view out loud, it becomes open for critique. It tells others where I stand so they don't have to guess. And if we don't agree, this might allow them to meet me closer to where I am. Then by picking apart the claims of others, it forces them to explain things better. Or by trying to incorporate parts of what they say into my own claims, I can reduce the surface area of any disagreement. I realize how easily that can come across as being obstinate. It's usually quite the opposite. I am trying to better understand opposing views by (selfishly perhaps) using the method that works best for me. I think something I could definitely work on here is finding more opportunities for open ended questions, which would give more control back to whoever I'm "arguing" with.

pez20:04:08

Written communication is a very blunt tool. So much information is not conveyed that we are otherwise relying on being conveyed. At least with me I tend to forget this, my intentions are obvious to me and I forget how not obvious they are to others. IRL a lot of this is compensated for by body language and eye contact. And on top of that it is this problem with that we are all so different. 😃 I now know better how to read your way of communicating, @U90R0EPHA. Still, you’ll make it easier for me if it doesn’t get to where we are almost arguing when we really rather are trying to figure things out together.

skylize20:04:42

Agreed. 😸

bringe21:04:28

> By presenting my view out loud, it becomes open for critique. It tells others where I stand so they don’t have to guess. And if we don’t agree, this might allow them to meet me closer to where I am. I’ve found myself communicating this way at times too, and I try to be more conscious of it now. > I think something I could definitely work on here is finding more opportunities for open ended questions I’ve found this strategy to be effective in the past for myself.

skylize21:04:00

> I’ve found myself communicating this way at times too, and I try to be more conscious of it now. > I try to be conscious of it too. A few years ago, I could have had everyone in the channel absolutely fuming ... and not even noticed there was anything wrong. :rolling_on_the_floor_laughing:

😄 2
🙃 1
pithyless14:04:26

As a bystander, just want to send some hugs and gratitude for the recurring themes in this thread: the introspection and ability to self-correct one's beliefs and behaviors; and the empathy and conviction to always try to find the best in people. It would have been so much easier to do otherwise. I hope I will have the presence of mind to remember these rules myself, next time I am inching towards a heated debate. :hugging_face: gratitude

4
gratitude 6
❤️ 2
Dustin Getz14:04:41

the comments were triggering to me too, I did not appreciate being subscribed to notifications of a back and forth argument and ultimately muted the thread (my thread) @U90R0EPHA you have not asked for feedback, you have only stated that you don't understand why (thus implicitly disclaiming responsibility for your contributions to the failed thread). So I am taking a risk here by giving unsolicited feedback. Here is a mental model for communication that has served me well: https://www.weskao.com/blog/strategy-not-self-expression#:~:text=Strategy%20is%20probably%2010%25%20of,the%20person%20to%20feel%20remorse.. I hope you find it helpful in understanding why the thread failed and at what point exactly the failure occured.

skylize15:04:02

> (thus implicitly disclaiming responsibility for your contributions to the failed thread) > I am explictly claiming full responsibility, with the caveat of trying to explain how the cause is that, in the context of typical expectations for communication, I am essentially "broken". I can do my best to continue improving my communication skills. But I'm not going to suddenly be a different person who communicates like everybody else does. If pez understood some of my differences better before your thread, there's a good chance your thread would not have run off the rails. > you have not asked for feedback > Feedback always welcome. > I hope you find it helpful in understanding why the thread failed and at what point exactly the failure occured. > No. Unfortunately I don't find it helpful. I was not trying to convince anyone to change their behavior. Would you care to explain how this strategy would have fit in?

skylize15:04:03

And @U09K620SG, I should also specifically apologize for ruining your thread. Sorry 🙏:skin-tone-2: