Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-10-04

Channels

#conjure
<
2022-10-04
>
nate15:10:14

would this be possible in a conjure addon?

Olical15:10:10

Hmm I wonder how it'd be implemented. I think not too bad with tree sitter but I think it'd be almost impossible without. You'd have to write a Clojure parser, so basically reinvent treesitter.

Olical15:10:21

So I think it's possible with TS, which is fine

Olical15:10:47

Would have to walk up to find the thread macro then drop the direct children below the cursor position. Then eval that

Olical15:10:49

Would have to be language specific and only useable in languages that have threading macros. So on a client by client basis + some small integration code to describe the behaviour. And then they can all reuse a bunch of shared code.

nate15:10:31

I wonder how the other editors do it, if it's delegated to cider or something or if they're rewriting clojure on the fly

dave15:10:12

If I'm not mistaken, I don't think this thing would need to know about threading macros. It could just be an "evaluate current form up to cursor" operation

Olical15:10:19

You'd need your cursor to be in a very specific spot though. Maybe that's fine. I was thinking it'd be smarter and walk outwards to the thread macro, but you're right. This could be generic at the expense of requiring more specific cursor placement.

dave15:10:40

Ah, yeah. I see your point

dave15:10:42

I think knowing about the thread macro could be worth the trouble of doing something more specific. I like the idea of being able to do something like this: 

(-> some-value
    (do-a :thing)
    (do-a :nother | :thing)
    (do-something :else))
and just move my cursor up and down and be able to eval the thread form up to the step that I'm currently on. The more generic version could be more annoying. I'd have to make sure that my cursor isn't inside of the parens of each form. At that point, I'm not sure I'd bother -- it might be easier at that point to do something like I'd do today and just comment out the remaining forms with #_ and eval the whole thing.

dave15:10:50

For example, (+ 1 2 3 | 4 5) would yield (+ 1 2 3) => 6

nate15:10:16

toss the rest of the forms or elements till it closes

Olical15:10:46

I would imagine others are doing some light Clojure parsing

Olical15:10:22

Or wrapping the code in some kind of macro code, quoting the body, and having the wrapper code work on the inner code-as-data

Martynas Maciulevičius17:10:09

My first idea is to use vim-sexp and use sexp_move_to_prev_bracket with visual mode. Then you could press <localleader>E. This is several keystrokes but it could probably be done with a command :thinking_face: So if you bind sexp_move_to_prev_bracket to ( then the key sequence could be this: v(<localleader>E. But this wouldn't insert the ) at the end and it would say that there's a syntax error. It could be fixed if evaluation function would try to balance the ending paren as it would only be one paren to handle.