Thomas Coenen

That's strange. Can you post your full rule? Does this happen only in simulation?

I could reproduce this with `echo: "{shell.output}"` in simulation. Because the shell command is not run the placeholder is not filled. I'm thinking about setting `shell.output` to `** simulation **`...

I'm glad it's working now 👍 In the next version you'll be able to specify the value of `{shell.output}` in the simulation (`** simulation **` by default). Just a note:...

The problem seems to be that the wrong config file is loaded. As you can see in `check --debug` output your config file is located at `C:\Users\Gnarf\AppData\Local\organize\organize\config.yaml` and contains ```yml...

Closing this as it was most likely simply the starter config file.

Sounds like a good idea and would be perfect for integration tests! I'll see what I can do. Do you have a JSON structure in mind?

I thought about this and one problem I see is that the JSON output only becomes valid after the run is completed. I think it would be nice to still...

I just tried it. `jq` works nicely with `JSONL`. If you want a single big json object after execution `--slurp` works great. I found some more info here: https://zxvf.org/post/jq-as-grep/ EDIT:...

If I understand this correctly you need a mechanism to detect if the file has ever been handled by organize, right? Most people just move the original file to a...

Good idea. Creating a website for this is a bit too much but a folder with some predefined rules would certainly be useful and could live in this repository. Goes...