Skip to content

Commit

Permalink
go-script-bash v1.1.2
Browse files Browse the repository at this point in the history
  • Loading branch information
mbland committed Dec 13, 2016
1 parent 22bace2 commit 6c44263
Show file tree
Hide file tree
Showing 3 changed files with 22 additions and 11 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,8 +195,8 @@ scripts can be in any other interpreted language.__
First you'll need a copy of this framework available in your project sources.
Archives are available at:

- https://github.com/mbland/go-script-bash/archive/v1.1.1.tar.gz
- https://github.com/mbland/go-script-bash/archive/v1.1.1.zip
- https://github.com/mbland/go-script-bash/archive/v1.1.2.tar.gz
- https://github.com/mbland/go-script-bash/archive/v1.1.2.zip

You can also add this repository to your project as a [`Git
submodule`](https://git-scm.com/book/en/v2/Git-Tools-Submodules):
Expand Down
27 changes: 19 additions & 8 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# go-script-bash v1.1.1
# go-script-bash v1.1.2

This is a bugfix release.

Expand All @@ -16,16 +16,27 @@ This software is made available as [Open Source software](https://opensource.org

## What's new in this release

### log: Replace `echo -e` with `printf`
### modules: Improved error handling for `. "$_GO_USE_MODULES"`

On at least one macOS 10.12.1 installation, `echo -e` under Bash 3.2.57(1)-release in Terminal.app wasn't converting `\e` sequences to actual ANSI escape sequences. Using `printf` instead resolves the issue.
Previously, the `$_GO_USE_MODULES` script would report an `Unknown module:` error in every error case, even if the module existed but failed for another reason ([Issue #25](https://github.com/mbland/go-script-bash/issues/25)). The module's standard error would also get redirected to `/dev/null`, which made diagnosis even more difficult.

## Changes since v1.1.0
Now any modules that actually exist but return an error when imported will be identified as such, rather than being reported as unknown, and standard error isn't redirected at all ([PR #26](https://github.com/mbland/go-script-bash/pull/26)).

## Changes since v1.1.1

<pre>
187715e Mike Bland <[email protected]>
Merge pull request #24 from mbland/printf-esc-seqs
22bace2 Mike Bland <[email protected]>
Merge pull request #26 from mbland/module-import

8833762 Mike Bland <[email protected]>
use: Improve module import error message

4bb94e2 Mike Bland <[email protected]>
use: Nest module file path tests

92bc468 Mike Bland <[email protected]>
use: Detect module path before sourcing

4bc05c8 Mike Bland <[email protected]>
log: Replace `echo -e` with `printf`
5ea7820 Mike Bland <[email protected]>
modules: Fix incorrect help text
</pre>
2 changes: 1 addition & 1 deletion go-core.bash
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ fi
# This and other variables are exported, so that command scripts written in
# languages other than Bash (and hence run in new processes) can access them.
# See `./go vars` and `./go help vars`.
declare -r -x _GO_CORE_VERSION='v1.1.1'
declare -r -x _GO_CORE_VERSION='v1.1.2'

# The URL of the framework's original source repository
declare -r -x _GO_CORE_URL='https://github.com/mbland/go-script-bash'
Expand Down

0 comments on commit 6c44263

Please sign in to comment.