Runscript 1.3.0 Release Candidate 2

Default positionals!

Adding $opt default_positionals to a runscript allows run to pass args which point to nonexistent targets to the default target instead, making it work more like a shell script. My recommendation is not to put it on everything, but only the scripts that need it.

The help message is now more helpful as well

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

As seems to be usual, there's a linker error preventing me from creating a windows build.

Runscript 1.3.0 Release Candidate 1

Environment variables!

Environment variables can now be created/overriden in a runscript using bash-like syntax (MY_VAR=value). They are evaluated at the line they are declared, and don't have their values change between command executions unless there's another line with an env override.

There is now a flag to list all the scripts in a runfile (with a fancy colour display too)

Command executions containing interpolated arguments now display the evaluated form next to them

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

No windows build for this pre-release due to a linker error.

Runscript 1.2.0

This "stabilises" rc.1, even though there hasn't been much testing anyway.

Full changelog of this version:

• run checks parent directories for Runfiles when resolving targets.
• Runscripts can include Runfiles.
• Error formatting made more shell-like
• Nonexistent positional arguments evaluate to "" instead of panicking

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

I cannot provide a Windows build for this release due to a linker error when cross-compiling.

Runscript 1.2.0 Release Candidate 1

Nonexistent positional arguments, such as in the following example, will evaluate to an empty string if they are left unspecified, instead of panicking.

$ cat run
test $1 '==' '' && echo 'yay!'
$ run

Errors in included files will print a message acknowledging the nested nature of the error, instead of panicking. This behaviour will be expanded into a 'stack trace' in the next minor version

Runscript 1.2.0 Pre-release 2

Two major changes in this pre-release.

Runscripts can include other runscripts. The syntax is $include file, where file is a file selector in the same format as described in the 'Targets' section of the readme. Formal documentation will come at some point.

The error formatting has been changed to remove the dependency on codespan-reporting, and to make it more shell-like

There is no windows build for this pre-release due to a known linking issue when cross-compiling from mac.

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

Runscript 1.2.0 Pre-release 1

This update makes run check parent directories for runscripts.

There's no windows binary for this pre-release due to a linker error.

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

Runscript 1.1.0

This release adds support for "simple" globs: only patterns with *, ?, and {} are going to expand properly, but nothing else.

Issues addressed:

• #1: "Simple" globs are now supported
• Recursive run calls can now be chained and piped

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

Runscript 1.0.1

Addresses some minor issues

• It is now possible to get version information with the --version flag
• Subcommands inherit standard input of parent, allowing the use of interactive programs such as lldb
• Nonexistent target errors now integrate with codespan

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

Runscript 1.0.0

The first stable release of runscript

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.

Runscript 1.0.0 release candidate 2

Used termcolor for phase messages

The attached binaries are not installers!
Simply decompress them, and they (should) work. Put them on your $PATH if you want.