I just used io/copy and GZIPInputStream , but a simple fs/(un)gzip might be useful to fill out the api

Sure!

Great, here is the pr: https://github.com/babashka/fs/pull/103

Nice! Note that #C03KCV7TM6F also does exactly that:

neil dep add reagent/reagent

Even though I already use Neil and https://github.com/teodorlu/neil-quickadd for dependencies already, I found it really interesting to read your code. It's so readable and straightforward! I didn't expect that neil dep add could be implemented in one page of code. (Though Neil supports finding dependencies on other places than Clojars)

neil also preserves whitespace/formatting

what, how come I've never heard of neil? 😆 This is great!

ah another difference is that babashka-neil add deps to only deps.edn ?

@U059WGT3F7C You can specify --deps-file

@U04V15CAJ will project.clj files work too?

@U059WGT3F7C currently not

I do have this slightly related util: https://github.com/borkdude/lein2deps, but it only works one way

you could combine this with #clj-kondo :locals analysis: https://github.com/clj-kondo/clj-kondo/blob/master/analysis/README.md

so find all the callsites of with-span (you can also do this with clj-kondo) and then find the local as argument and then find the local-definition, then read the expression at the location of the local-definition (e.g. using rewrite-clj or edamame, etc)

Interesting. This gives me something to explore. I will likely have doubts on how to do > then find the local-definition, then read the expression at the location of the local-definition but let me try on my own first. Thanks!

Feel free to come back with more questions

Using the clj-kondo analysis I found the location of the local definition.

{:end-row 794,
 :scope-end-row 876,
 :name span-attrs,
 :scope-end-col 55,
 :filename "src/some-path.clj",
 :str "span-attrs",
 :col 9,
 :id 287,
 :end-col 19,
 :row 794}

@U0A5B1LJU It's probably best to use rewrite-clj and write a loop like this: https://github.com/borkdude/carve/blob/cb621317ae1582869c8bd8f1a47cf57a3598d803/src/carve/impl.clj#L124 Just parse top level expressions until you find the one with the right row + end-row and then search for the sub-expression with the right location and then stringify that

A similar thing can be done with edamame

Let me write an edamame example for you

> Just parse top level expressions until you find the one with the right row + end-row and then search for the sub-expression with the right location and then stringify that thank you for this algorithm. I managed to write some hardcoded code using rewrite-clj that gave the expected answer. now to refine it further.

with edamame, I couldn't figure out how to get the end-line number. with rewrite-clj, their position-span function helped a lot.

with edamame, the end-line number is on the metadata of the parsed form :)

sorry, I got distracted, but glad you figured it out

I did check the meta. In the readme, it shows the start and end line numbers. However, when I was trying it, I was only getting a line number. I must have been doing something wrong Will check it later.

user=> (require '[edamame.core :as e])
nil
user=> (meta (e/parse-string "foo"))
{:row 1, :col 1, :end-row 1, :end-col 4}

end-row and end-col

You are right. I misunderstood this as a recommended set of options

{:all true
 :row-key :line
 :col-key :column
 :end-location false
 :location? seq?}