You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+19-8Lines changed: 19 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# go-script-bash v1.1.1
1
+
# go-script-bash v1.1.2
2
2
3
3
This is a bugfix release.
4
4
@@ -16,16 +16,27 @@ This software is made available as [Open Source software](https://opensource.org
16
16
17
17
## What's new in this release
18
18
19
-
### log: Replace `echo -e` with `printf`
19
+
### modules: Improved error handling for `. "$_GO_USE_MODULES"`
20
20
21
-
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.
21
+
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.
22
22
23
-
## Changes since v1.1.0
23
+
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)).
24
+
25
+
## Changes since v1.1.1
24
26
25
27
<pre>
26
-
187715e Mike Bland <mbland@acm.org>
27
-
Merge pull request #24 from mbland/printf-esc-seqs
0 commit comments