Zander Hill

> @zph sounds good! I'd love a contribution. Ok :) I'll find time and pull out those changes for a PR

Reason for wanting this: - We're using a multi-language tome project that includes mainly typescript, python, bash - Because this comment flexibility is missing, we can't use help declarations in...

If there's an appetite for using a 3rd party library, we could use https://docs.rs/syntect/latest/syntect/parsing/struct.SyntaxSet.html#method.find_syntax_for_file (Potentially but un-researched) Then pull out the definition from sublime-syntax definitions ([ref?](https://docs.rs/syntect/latest/syntect/parsing/syntax_definition/struct.SyntaxDefinition.html?search=)) to determine what comment...

I prototyped it using a combination of filename extensions or falling back to parsing the shebang: https://github.com/zph/tome/blob/54329a3d298af75fd48279b1cd550330b44db22c/src/script.rs#L68-L88 If you're interested I can pull it out and contribute upstream 🖖

Fixed if we incorporate the CI setup I setup here: https://github.com/zph/tome/blob/master/.github/workflows/main.yml. That CI workflow updates the brew recipe for each release.

Adding more background: Failing on my mac when run under fish and bash shell. Head of output: ``` bash-5.2$ cargo test Finished test [unoptimized + debuginfo] target(s) in 0.02s Running...

With backtrace: ``` ❯ RUST_BACKTRACE=1 cargo test Finished test [unoptimized + debuginfo] target(s) in 0.05s Running unittests src/lib.rs (target/debug/deps/tome-ca586cb57dc09330) running 29 tests test commands::tests::test_should_not_source ... ok test commands::tests::test_should_source ... ok...

It's a platform issue w/ aarch64 on Mac (silicon) and Linux: https://github.com/zph/tome/actions/runs/8126166576/job/22209542959

@bartlomieju Thank you for the quick reply :). I thought about abstractly how to do this last night and only came up with complicated approaches that would need to involve...

Here's the blog post about using the dynamic runbooks where I mention and credit dax: https://plaid.com/blog/switching-to-tidb/