Out of curiosity, what does #_" represent? I usually just go with the regular comment syntax for that given language, so ; vim: set ft=clojure:

@U7ERLH6JX might also know as a vim user

@U01KUQRDMLG standard clojure comment like the one @U0422G22932 said would work, (n)vim looks for set patterns in the first line, doesnt need to start with #

@U0422G22932 the #_ is the clojure reader dispatch character to ignore the next form. in this case the string following it

can comment out forms in a form like (-> foo (bar a) #_(baz b) (quz c))

cool thanks. @U04V15CAJ i think you use emacs. Do you do #_"..." or ; -*- mode: clojure; -*-?

Yeah #_ is nice because you can comment out a form that has other forms on the same line, or a form that spans lines

I might have used the latter

tyty

have used? Are you on vscode now? 😜

doesn't have used mean that you're still doing it? like "have been" etc? ;-)

perfect tense implies an ended action

I have been using the latter, maybe

don't remember, I don't do this often

have been using vs. have used, the former adds a participle using to sort of reimply it's continuing 😛

#C0400TZENE7 takes care of this for you ;)

Ah, you don't use standalone chmod +x bb scripts?

oh. Will check it out!

@U01KUQRDMLG Here are some of my scripts that you can install with bbin: https://github.com/borkdude/tools

cool thanks again

I think in emacs I just enable clojure-mode manually as well, if needed. I add the mode-line for github highlighting though

I'd go with a ~/.bb.edn maybe and refer all of these scripts as tasks. then have aliases to bb --config ~/.bb.edn <task-name>

You can do that but you can also just write libraries to compose things together and then make script entry points to call into those libraries.

Btw, I don't recommend putting a bb.edn in your home root folder, since clojure-lsp etc might recognize your entire home directory as a giant clojure project

yeah fair point

i have my aliases pointing to a dir of bb.edn and the tasks

I'm not sure I know what you mean with script entry point here, do you have any articles or reference-projects to illustrate?

@U0422G22932 an example is lein2deps, which itself is a library but the "front-end" script uses this library. The script lives here and can be installed using #babashka-bbin

bbin install 

The front-end script is just a thin wrapper:

(require '[babashka.deps :as deps])
(deps/add-deps '{:deps {io.github.borkdude/lein2deps {:git/sha "60e33d969f624143f03ebd3456a703e68c8b9ab7"}}})
(require '[lein2deps.api])
(apply lein2deps.api/-main *command-line-args*)

@U7ERLH6JX’s approach works well if you're not planning to have your code on github etc, but even then you could use the "library" approach using :local/root

Everything will be on GitHub, my primary concern is just to keep the friction of producing new scripts as low as possible, without ending up with maven-style project hierarchies for what is basically a single, independent function. I guess I just need some more experience with building proper libraries

I recommend checking out #C0400TZENE7

I'll take a look at your examples, yeah! Also, while you're here; I've been through several of your talks/podcasts, and I really appreciate your feedback and your work. Thank you!

if you're writing a tool that you want to install just once, maybe it makes sense to use #C03KJHCNZ99 to implement subcommands

e.g.

bbin install io.github.borkdude/quickblog --tool --ns-default quickblog.api

quickblog new 
quickblog watch 
;; etc

Yeah i've been using go+cobra for this previously, but babashka-cli is the best clojure-alternative I've seen for that so far