Invalid string error about xdg-ninja HOT 5 CLOSED

This is happening due to the fact that echo behaves differently between bash and dash:

 $ cat /tmp/test.sh
#/bin/sh
echo "One\nTwo"
 $ bash /tmp/test.sh
One\nTwo
 $ dash /tmp/test.sh
One
Two

and from what I can read, jq is following JSON guidelines, which means forbidding multi-line strings with double quotes.

On bash, it works fine as the JSON given has a plain \n, whereas on dash, it has a literal newline, which breaks the program.

I'd say that there is no real reason to send the data from the plain JSON files to stdout when jq already can parse from a file via CLI. I published a fix in #23.

From Wikipedia:

Nowadays, several incompatible implementations of echo exist on different operating systems (often several on the same system), some of them expanding escape sequences by default, some of them not, some of them accepting options (the list of which varying with implementations), some of them not.

The POSIX specification of echo leaves the behaviour unspecified if the first argument is -n or any argument contain backslash characters while the Unix specification (XSI option in POSIX) mandates the expansion of (some) sequences and does not allow any option processing. In practice, many echo implementations are not compliant in the default environment.

Because of these variations in behaviour, echo is considered a non-portable command on Unix-like systems and the printf command (where available, introduced by Ninth Edition Unix) is preferred instead.

from xdg-ninja.

That's pretty weird, what do you have /bin/sh symlinked to?

from xdg-ninja.

It's linking to /bin/dash.

from xdg-ninja.

I don't have any experience with that unfortunately, maybe @Ballasi could take a look at this as well?

from xdg-ninja.

I'm using KDE Neon, which is based on Ubuntu. Please let me know if you want to know any more details.

from xdg-ninja.