Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up on #142
This adds
files
, which allows creating (=linking) files into the devenv directory. This adds the following options:Only one of these options may be set for each file.
name
indicates the name/path of the file. For example:Will create a file
$DEVENV_ROOT/some/file.txt
.The test
tests/files/devenv.nix
shows more basic examples of each supported format.I'm on the fence whether the internal options are useful. The intention was to still be able to override the format ini that has different options, even though this isn't supported by the docs.
I did drop the support for
files.<name>.executable
, it didn't make much sense for most of the formats. It could've been fortext
, but then I'd rather see something likescript
that uses aninterpreter
option to be used in the shebang. That said, it's still possible to create such a script with the internal options.