compile_commands.json breaks when paths contain spaces

[WebFreak001]

the file property isn't really defined what exactly it holds, so it's kinda implementation defined and reggae puts multiple files in it, space separated - which would break for consumers trying to split just by spaces, because file names with spaces are not escaped.

Furthermore the commands in command are also not escaped and contain stuff like

"command": "/usr/bin/dmd -makedeps=.reggae/objs/./gdb-test.objs/GDB Test/source_app.o.dep -debug -g -w -version=Have_gdb_test '-I/home/webfreak/dev/GDB Test/source/' -of.reggae/objs/./gdb-test.objs/GDB Test/source_app.o -color=on -c /home/webfreak/dev/GDB Test/source/app.d /home/webfreak/dev/GDB Test/source/baz.d /home/webfreak/dev/GDB Test/source/scope.d /home/webfreak/dev/GDB Test/source/xd.d"

which would just break if you were to try to run them like this.

[atilaneves]

What would the solution be? It can't be to add backslashes before the spaces, since that wouldn't be a valid JSON string anymore.

[WebFreak001]

backslash would work, quotes would work, just anything that makes the shell run the command properly when run

[nordlow]

As I already wrote at #303 (comment), some string literal escape sequences are missing an extra backslash. It might be as simple as replacing every string literal backslash with two backslashes.