Sven Kanoldt

Maybe you can try out the `pre` hooks, there is an example in the repo: https://github.com/cargo-generate/cargo-generate/blob/main/example-templates/hooks/cargo-generate.toml#L6 This actually should allow you to change the contents as you like.

also, since you're running on macOS, there are some [issues with sed](https://stackoverflow.com/a/19457213/1252968) I would suggest using `gsed` (the linux gnu sed), then the arguments as you have described them should...

I tried to reproduce the issue, but I cant. Please have a look at the code: https://github.com/cargo-generate/cargo-generate/pull/1392/files#diff-8d7079762a7191390b9114d55ccc9b5272eb29e370358108848fc696150150fd There I have several rhai initiated sed calls, and they produce exactly what...

@Nejat I wonder if you could have a look at the PR https://github.com/cargo-generate/cargo-generate/pull/1392 and see it has any impact on your issue described here? Maybe it solved it even?

Despite that being pretty much opinionated, could you be more specific about your confusion and what exactly did not behave correctly with the logs?

Maybe I don't understand your definition or expectation of `destination`. Maybe you can elaborate it? I have tried combinations of using `--destination`, `--init`, and both. The results look consistent to...

For comparision I'm explaining how `cargo new` and `cargo init` are operating: ```sh ❯ cargo new --bin foobar2 ❯ ll foobar2/ total 8 -rw-r--r--@ 1 I563162 staff 78B Feb 25...

Hey @tommygarvin, thanks for your efforts. Do you think you can have a look at the merge conflicts and get them sorted? Then we could proceed landing this one.

@tommygarvin could you pls have a look at the merge conflicts, then I would like to merge it.

Thanks a lot @tommygarvin for your contribution. 🫶