This update has introduced another potential breaking change for your
safety: zero length arrays now fail by default. Also errors inside
subshells will cause the parent command to fail if ran inside a
try
or trypipe
block.
echo @{g this-file-does-not-exist}
) should fail by default,
like unset variables. This is enabled by default but can be disabled via
config: set proc strict-arrays false
@g echo this-file-does-not-exist.*
try
and trypipe
blocks. eg
try { echo ${false} }
function
now supports defining parameters&&
eg
do-something && do-something-else
for chaining
successful commands||
eg
do-something || do-something-else
for chaining unsuccessful
commandsconfig: set shell titlebar-func { block }
titlebar-func
can also be written to your
tmux
window title via
config: set shell tmux-echo true
.$HOSTNAME
$1
(and upwards) which
correlates to the scope’s parameter index. $1
is the
functions first parameter. $2
is the second.
$13
is the thirteenth.$0
which contains the
function nameonCommandCompletion
(this is experimental
and subject to change in the next release)echo Hello ^$name
will prompt
the user to enter a name. Macro variables are only support in the
REPLread
now supports flags (eg default option, etc) to
allow for a better experience in shell scriptingonKeyPress
events. This no
longer produces an error forcing you to remove the old event before
adding the new oneopenagent
builtinforceTTY
:
config: get proc force-tty false
set by default, which then
proxies stderr and prints them in redonFilesystemChange
where fileRef
is not getting passed correctlyonFilesystemChange
where path is
zero length stringcount
should check if it is a methodmurex-docs
still referred to len
builtin. That should be changed to count
Published: 15.05.2022 at 22:49
open
” (openagent
): Creates a handler
function for open
event
): Event driven programming for shell
scriptsfunction
): Define a function blockread
): read
a line of input from the user
and store as a variableconfig
): Query or define Murex runtime settings&&
And
Logical Operator: Continues next operation if previous operation
passes||
Or Logical
Operator: Continues next operation only if previous operation
failsThis document was generated from gen/changelog/v2.7_doc.yaml.
This site's content is rebuilt automatically from murex's source code after each merge to the master
branch. Downloadable murex binaries are also built with the website.
Last built on Wed Jan 15 23:07:50 UTC 2025 against commit b4c4296b4c429617fd41527ea0efef33c52c15ef2b64972.
Current version is 6.4.2063 (develop) which has been verified against tests cases.