the following will take the output from a json object and flatten it into a key-value path. this is particularly handy when you’re looking to parse out the supported paths in a given device. note: you need to remove the \s from this output and put the entire jq string on the same line. jq '[leaf_paths as $path \ | {"key": $path | join("/"), "value": getpath($path)}] \ | from_entries' foo.json alias to make life happy....
i really don’t know how i would use this implementation of vim on the ipad given that it doesn’t appear to have dropbox support. but i really like the fact that it exists and it’s getting downloaded instantly. i’m more of an emacs guy myself, but i’m perfectly conversant in and happy to get stuff done in vim. particularly given the sad state of editors on the ipad. i do fear however that the inability to ship vim with an external binary will limit its ability to support cloud filesystems....
once upon a time people loved quicken. quicken was intuitive (and the company was more or less named along those lines) and it just worked. then along came microsoft money. i, a blue blooded devotee of everything UNIX, embraced that application with both arms and i might have on occasion tried to dry hump it. yes, i loved that app. then $MSFT decided that they were going to kill that product....