Fldigi - Kambing UI

Detection of existing scripts
In anticipation of a collection of useful "fldigi scripts", the macro browser contains a macro line for each
executable file found in the scripts directory.
The EXEC macro allows the text that is read from the child process to be parsed for more fldigi macros. For
example, try this macro:
cat foo
where foo is a file that contains:
This may have some interesting uses but, if it is undesirable, it can be suppressed with an extra layer of
redirection. Instead of command, you would use noexp command where
noexp is the following very simple script:
snip---------------------------------------
#!/bin/bash
echo -n ""
"$@" # run the command
r=$? # save its exit code
echo -n ""
exit $?
snip---------------------------------------
There are three additional MACRO definitions that expand the capability of the command: ,
and .
The and macros stop and resume the expansion of all strings. For example,
would only expand the second . By wrapping the
command output in this way we can be sure that no text will be expanded. You might even use
"$@" | sed "s///g"
if you feel paranoid.
FldigiContents Exec Macro
You can "fork and forget" with an exec macro defined as: exec command -args >/dev/null
Any of the text that appears between the and can reference an executable program or shell
command found in the ~/.fldigi/scripts directory.
Any text output that is returned by the program or script program (or the result of the in-line command) is always
returned to the transmit buffer and appears as appended to the transmit window.
Detection of existing scripts 92