cloudcmd v5.13.0

Added ability to show more details when configuration file ~/.cloudcmd.json can not be parsed.
If you forget to put end quotes and comma:

{
    "editor": "edward
}

You saw something like this:

coderaiser@cloudcmd:~$ cloudcmd
cloudcmd --config ~/.cloudcmd.json: Unexpected string in JSON at position 29

Now you will get more information about source of an issue.

coderaiser@cloudcmd:~$ cloudcmd
cloudcmd --config ~/.cloudcmd.json: Unexpected token ' ' at 1:23
    "editor": "edward

feature

• (cloudcmd) show line number when config is not valid json (closes #98)
• (edit) add setValue
• (edit) show: rm this