Releases: toumorokoshi/tome
Releases · toumorokoshi/tome
v0.11.1
v0.11.0
What's Changed
- add TOME_SCRIPT_ROOT environment variable by @toumorokoshi in #46
Full Changelog: v0.10.0...v0.11.0
v0.10.0
v0.9.0
The 0.9 series should be the final version of tome before a 1.0
release.
This includes a couple breaking changes, and users should update
their scripts:
- the following commands are now builtins, and will overrides any scripts with the same name: commands, exec, help, tome.
- tome no longer infers the shell from the SHELL environment variable in
any situation: users should pass in the desired shell directly during the initialization. - a script must be explicitly be marked with COMPLETE to support
completion. Previously all scripts were assumed to support completion.
What's Changed
- Adding reserved commands by @toumorokoshi in #31
- adding support for exec by @toumorokoshi in #32
- Require "COMPLETION" flag to complete script by @toumorokoshi in #34
- require shell to be passed in by @toumorokoshi in #35
- changing flag for completion support to COMPLETE by @toumorokoshi in #36
Full Changelog: v0.8.1...v0.9.0
v0.8.1
fix completion for tome names with 2+ chars (#30) fix #28 (GitHub) tome completion was failing for a command "app", when navigating to sub directories. This was occurring due to incorrect stripping of the first word in completion, instead stripping the first 2 chars. some minor style fixes.
v0.8.0b0
minor: adding e2e tests (#27) Adding end-to-end tests to sanity check tome builds. The zsh / bash completion logic wasn't working for non-interactive initial invocations for zsh (needed for CI), so added a -C flag to silence the interactive portion. The fish shell needed it's own e2e script and variants of scripts for sourcing.
v0.7.5
include support for OSX "-zsh" (#20)
v0.7.4
first build published via GitHub actions. No code changes.
bugfix: args now passed to non-source scripts
Fixes #16. Previously arguments were not passed into non-source scripts, which made common use cases of parameterized scripts impossible.
bugfix: add clearer message for commands not found in directories
Adding messages when argument is a directory The previous error message when one selects a command that doesn't exist in a subdirectory was unhelpful.