Is there a way to have two modify script for same target file ? On per OS ?

[cderv]

I have managed to handle a file using a modify_ script with the .ps1 extension for Windows, and I would like to handle the same file on Linux using a .sh script.

.ps1 script can't run on my Linux environment, so I get error like exec format error

Ideally, this would be the same target file, so I don't know how to ignore it properly, as I need to ignore the source.

Should I use .chezmoiscripts instead so that I can ignore each script?

Or is there a way to have two modify_ scripts for the same target?

[cderv]

Oh in fact I tried

{{- if ne .chezmoi.os "windows" }}
<target-file-name>.ps1
{{- end }}

and it worked...

I did not expect that from chezmoiignore documentation.

[twpayne]

Yup, that works. .chezmoiignore can be used to skip scripts, but this currently not documented as I've not come up with a good way to explain how it works, even though it makes sense to me.

Roughly speaking, scripts are treated as virtual targets and can be ignored. The name of the virtual target is the script with its attributes stripped (e.g. dot_dir/run_after_foo.sh has the virtual target name .dir/foo.sh).

[cderv]

Yup, that works. .chezmoiignore can be used to skip scripts, but this currently not documented as I've not come up with a good way to explain how it works, even though it makes sense to me.

Good to know I found the right way. And yes, it makes sense and I guess that is why I tried it after writing my question.

Roughly speaking, scripts are treated as virtual targets and can be ignored. The name of the virtual target is the script with its attributes stripped (e.g. dot_dir/run_after_foo.sh has the virtual target name .dir/foo.sh).

And for modify_ script the final target is the path without script extension right ?

dot_dir/modify_foo.toml.sh => This will read the target .dir/foo.toml in stdin. The script will process modify and write stdout in the target file, which will be .dir/foo.toml

Am I right on this?

Does this mean .chezmoiignore can be either .dir/foo.toml.sh or .dir/foo.toml in that case ?

[twpayne]

And for modify_ script the final target is the path without script extension right ?

Yes, this is correct. It's really an interpreter extension than a script extension. By default, interpreters are only configured on Windows, which means that, by default, no extension is removed on non-Windows systems.

Does this mean .chezmoiignore can be either .dir/foo.toml.sh or .dir/foo.toml in that case ?

It will be .dir/foo.toml. To quickly check this, run chezmoi managed which lists all managed targets.

[cderv]

By default, interpreters are only configured on Windows, which means that, by default, no extension is removed on non-Windows systems.

Oh good to know. I did not get this specifity. It makes sense.

It will be .dir/foo.toml. To quickly check this, run chezmoi managed which lists all managed targets.

Got it. Thanks a lot for your help and your time to explain. And thank you for this awesome tool !

[eugenesvk]

upd: think manually adding an extension like sh to the interpreters: section of chezmo.yaml init file may solve it!! Then you can have modify_foo.toml.sh on Linux while also having the extension .sh stripped, and now you can ignore one extension on one platform and another - on another

Have you managed to solve it? Since on nonWin extensions aren't removed, modify_foo.toml.sh will result in foo.toml.sh, so for foo.toml you'd need to use a shebang inside modify_foo.toml.

But then you'd have to files

• modify_foo.toml (shebanged, Linux)
• modify_foo.toml.ps1 (extension, Windows)

On Linux you can simply ignore the ps1 file, and the shebanged version will work with the toml target.

But then on Windows if you try to ignore the shebanged file by ignoring foo.toml, this prevents .ps1 modification from working since it thinks that the target is ignored
And if on Windows you don't ignore anything, you have an inconsistent state conflict where 2 files are targetting the same target (one "literal", another script with a silently stripped extension).