andrewchambers

More thought is needed, but so far the best idea is a hybrid approach allowing the mixture of parsed strings, and janet symbols: ``` ($ "ls (+ 1 2 3)...

Right now I don't have the time budget to fix this, but maybe in the future.

@ALSchwalm depending on how this is addressed, it also affects completions.

I am starting to think "Confusing behavior" means a tutorial problem and not a technical one we can solve in a sensible way without forking janet (besides the keyword issue,...

@mirzazulfan I'm not sure I can see the J in your proposed logo, I'm also not sure what you mean by 'the icon code'. I don't have too many ideas...

Here is a gallery entry that needs to be added: https://acha.ninja/blog/json-in-janet-shell/

What version of janet are you using? It is also possible to specify the path to janet headers with ./configure --with-janet-cflags "-I/some/path/to/your/headers" Note, I haven't tried janet shell on macOS...

Interesting, there must be something different about readline on macos. I don't ever reference readline/rlstdc.h directly in my code, so it seems more like macOS doing something strange like not...

After you run ./configure the configuration script writes a file called config.inc in the janetsh directory, that file has some build parameters.

Hmm, seems we need to do something mac specific when linking.