{"push_id":992727692,"size":1,"distinct_size":1,"ref":"refs/heads/readme-refresh","head":"a579dacec55bea1a6599be9a053b09826890ed1e","before":"0ba985e9563e53c86e0a2ee78b2b629e3e47c0b6","commits":[{"sha":"a579dacec55bea1a6599be9a053b09826890ed1e","author":{"email":"8b27323fb6d62f5e86361e8f8ff85a3c0b4ea967@gmail.com","name":"Zhiming Wang"},"message":"Refresh README.md\n\nChanges that I cared to remember\n\n* Use proper Markdown instead of a rather awkward and inconsistent mix\n  of Markdown and HTML that\n\n    1. Defies tooling (e.g., using Pandoc to generate groff from it);\n    2. Doesn't help with readability;\n\n* Completely reworked installation instructions — hopefully more logical\n  now. Other than reorganization, here are the changes in substance:\n\n    1. `sudo` is not always needed (for instance, on my personal OS X\n       system I've changed the mode of `/usr/local` so that it belongs\n       to me and I write access — which is the default of Homebrew, by\n       the way), so leave that bit to the user with a suitable\n       explanation;\n    2. Added instructions on `PREFIX`;\n    3. Removed the bit about `chmod +x googler`; `googler` already has\n       mode 755 in this repo;\n    4. Added a link to Linuxbrew;\n\n* Removed references to `~/.bashrc` because:\n\n    1. Not everyone use bash;\n\n    2. Even for bash users, `~/.bashrc` could be a non-solution because\n       an interactive login session only reads from\n       `~/.bash_profile` (or fallbacks), not `~/.bashrc`, so referring\n       to `~/.bashrc` only adds confusion;\n\n    3. Most importantly, rather than giving quick instructions to\n       users (oh, just add this line to `~/.bashrc` and you're good),\n       I'd rather see them do independent research on aliases or\n       environment variables if they have never encountered them —\n       I (used to) answer questions on the bash and zsh tags of\n       StackOverflow, and I've seen way too many problems stemming from\n       usersmindlessly following half-baked instructions with zero\n       understanding of shell runcoms, and later turning their runcoms\n       into into an insalvagable mess. Fish shell is an outlier that is\n       not remotely POSIX, so specific instructions are fine.\n\n* Removed the note \"Google ignores searches for negative numbers\" since\n  it's misleading: it's not that Google ignores negative numbers, but\n  rather, Google search allows inline logic, and -*word* means to\n  exclude *word*;\n\n* Removed the warning \"`2>&1` would error as the console geometry is\n  calculated from stderr\", since we already removed that\n  restriction (softwrapping provided by terminal emulators is used in\n  that case; not as nice as hardwrapping on word boundaries, but\n  infinitely better than erroring out).\n\n* Regarding \"Look up n, p, g co or a number at navigation prompt\":\n  Removed the whole printout, because it's not really necessary (I\n  believe users could understand what's being said even without that\n  visual context), and who knows if the format of that prompt will ever\n  change and outdate this entry. It's usually bad to be way too specific\n  in docs because docs can hardly keep up with development ;)\n\n* Some minor improvements here and there.\n\n[ci skip]","distinct":true,"url":"https://api.github.com/repos/zmwangx/googler/commits/a579dacec55bea1a6599be9a053b09826890ed1e"}]}