@dutch_wolf it improves legibility if you surround code here on discuss in single backticks if it’s inline, like this:
This example code `$code=here` does nothing.
which produces this: This example code $code=here does nothing.
or between three backticks before/after if it spans multiple lines, like this:
This example code spans several lines:
```
#!/usr/bin/env bash
repo=“HOME/repo-rt" if [[ ! -d "{repo}” ]]; then blabla
```
which produces this:
This example code spans several lines:
#!/usr/bin/env bash
repo="$HOME/repo-rt"
if [[ ! -d "${repo}" ]]; then blabla
Now, if I read your example code correctly:
(also for some reason replacing the "-add "$k with ‘"-add "$k’ doesn’t work here)
then you can’t do that. If the code relies on parameter expansion in Bash as opposed to by G’MIC, then characters with special meaning, such as $, may not be single-quoted because that removes their special meaning. But k={6*($>+1)} does not look like Bash, meaning G’MIC is supposed to solve that, in which case you can surround it by single quotes.
I can help you with Bash, but I am clueless about G’MIC syntax.