v6.2
v6.2
Bug fix release
v6.2.4000
Breaking Changes
None
Features
- docs: minor updates to docs + website
Bug Fixes
- core: regression bug when comparing a non-str string (eg generic) with a string (issue #845)
v6.2.3000
Breaking Changes
None
Deprecation Warnings
Please read out compatibility commitment to understand how features are deprecated.
the
?
pipe is deprecated to make way for a the ternary operator. You can achieve the same result with<err> <!out>
, egcommand <err> <!out> parameters... | next-command ...
. It will be officially removed in v7.0the
=
andlet
builtins are deprecated and will be removed in v7.0. They've been marked as deprecated in the documentation for several versions but you'll now receive a deprecation warning when using them. This warning will not impact any functions that call them (they bypass the stdout and stderr pipes and write directly to your TTY). The change is very simple, Murex supported expressions as first class primitives, so you can simply drop the=
andlet
command names from your expressionsautomatic conversion of backtick
`
to single quote'
has been deprecated and will be removed in v7.0. The only reason this ever existed was a hack to enable quotes in=
. Worse still, this behaviour wasn't documented anywhere
Features
Features marked as EXPERIMENTAL are provided without assurances of future breaking changes. All other features are considered stable as part of Murex's compatibility commitment.
preview: progress bar to show how far through the preview document
docs: more improvements to documentation
Bug Fixes
caching: suppress cache.db connect message when in debug mode (issue #825)
murex-package
: package errors should be ignored inmurex-package list
(issue #826 docs)export
: exporting a non-existing variable would cause a crash (issue #824)murex-docs
: integrations docs were missing from compiled executable (read more)integrations: ChatGPT preview instructions were incorrect (read more)
core: crash handler was always disabled due to incorrectly flipping a boolean
expr
: re-write of==
and!=
operators to fix comparison bugs (issue #831 docs)expr
: when run as a statement, only the first parameter was used (issue #827 docs)expr
: panic when converting arrays and objects to a numeric scala (issue #829 docs)expr
::
was treated as<
in expressions (issue #832 docs)expr
: empty arrays returnnull
(docs))core:
go test
compilation errors on Windows fixedreadline: in preview, backspace characters where not pushing character positions (this bug only appeared in previewing UNIX man pages)
readline: final character in preview checked to see if it is a wide character
readline: tab widths in preview off by one
Special Thanks
Thank yous for this release goes to everyone in the discussions group plus all who raise bug reports.
You rock!
Published: 19.07.2024 at 08:54
See Also
- ChatGPT: How to enable ChatGPT hints
- Define Environmental Variable (
export
): Define an environmental variable and set it's value - Expressions (
expr
): Expressions: mathematical, string comparisons, logical operators - How To Contribute: Murex is community project. We gratefully accept contributions
- Murex Package Management (
murex-package
): Murex's package manager - Murex's Offline Documentation (
murex-docs
): Displays the man pages for Murex builtins - Operators And Tokens: All supported operators and tokens
This document was generated from gen/changelog/v6.2_doc.yaml.