4 ms·

howdoi beahaves in a very different way. It doesn't give you unix.stackexchange.com answers by default: $ howdoi unzip bz2 readcsvbz2file <- read.csv(bzfile("

howdoi beahaves in a very different way. It doesn't give you unix.stackexchange.com answers by default: $ howdoi unzip bz2 readcsvbz2file <- read.csv(bzfile("file.csv.bz2")) how2 switches API depending on what language you are querying.

danso 11y ago
It's also much nicer looking and more interactive, FWIW...I also agree with its defaults. $ howdoi inverse grep a file Simply pops this up: $ grep -L "foo" * ...apparently it scrapes the answer result and print the last occurrence of code-formatted text. Whereas `how2` pretty-prints the entire answer, narrative and code, so I know what the respondent was actually addressing. FWIW, both tools don't address what I want (I was thinking `grep -v`)...but that's not a fault of the tools, but of the ambiguity in how we ask questions. `howdoi` has far more faith in there being "Just One Answer"...where `how2` let's you move very quickly between the relevant choices, giving you the right amount of context to navigate. Well done OP!
- gnufied 11y ago
  Uh oh, ~> howdoi parse json python {"maps":[{"id":"blabla","iscategorical":"0"}, {"id":"blabla","iscategorical":"0"}], "masks":{"id":"valore"}, "om_points":"value", "parameters":{"id":"valore"} } Yep can't agree more.
- metakermit 11y ago
  You can also get the whole answer in `howdoi` by passing the `-a` flag: howdoi -a inverse grep a file Even basic syntax highlighting is supported using `-c`.
  - danso 11y ago
    The difference is that it's verbosity and pretty-print is the default for how2, and I think that's the more sensible choice, because it saves me the trouble of having to remember how to invoke it with flags just to get decent output from it. By the time I need to seek help, I'm willing to put up with verbosity.
    - mixmastamyk 11y ago
      Yes, though easily fixed: alias howdoi="howdoi -a -c " The other improvements from how2 being a curses app are helpful though.
- softawre 11y ago
  Funny enough, `how2 grep` does give you want you want.

danso 11y ago

It's also much nicer looking and more interactive, FWIW...I also agree with its defaults. $ howdoi inverse grep a file Simply pops this up: $ grep -L "foo" * ...apparently it scrapes the answer result and print the last occurrence of code-formatted text. Whereas `how2` pretty-prints the entire answer, narrative and code, so I know what the respondent was actually addressing. FWIW, both tools don't address what I want (I was thinking `grep -v`)...but that's not a fault of the tools, but of the ambiguity in how we ask questions. `howdoi` has far more faith in there being "Just One Answer"...where `how2` let's you move very quickly between the relevant choices, giving you the right amount of context to navigate. Well done OP!

gnufied 11y ago
Uh oh, ~> howdoi parse json python {"maps":[{"id":"blabla","iscategorical":"0"}, {"id":"blabla","iscategorical":"0"}], "masks":{"id":"valore"}, "om_points":"value", "parameters":{"id":"valore"} } Yep can't agree more.
metakermit 11y ago
You can also get the whole answer in `howdoi` by passing the `-a` flag: howdoi -a inverse grep a file Even basic syntax highlighting is supported using `-c`.
- danso 11y ago
  The difference is that it's verbosity and pretty-print is the default for how2, and I think that's the more sensible choice, because it saves me the trouble of having to remember how to invoke it with flags just to get decent output from it. By the time I need to seek help, I'm willing to put up with verbosity.
  - mixmastamyk 11y ago
    Yes, though easily fixed: alias howdoi="howdoi -a -c " The other improvements from how2 being a curses app are helpful though.
softawre 11y ago
Funny enough, `how2 grep` does give you want you want.