Discussion: remove the --exact option and make it default
=========================================================
Say you run `googler googler`. The word "googler" doesn't even appear once in the results. What the ...? Oh, Google is showing results for "google". But there's no indication whatsoever of this autocorrect in our output; sure, we can introduce more complexity in the parser to detect "Showing results for ...", but just like the result count, this doesn't sit well with our entry-based parser and printer, and is especially problematic with serialized output (`--json`), unless we completely break the interface.
Moreover, autocorrection simply isn't what people expect from command line utilities (autocorrect in interactive shell's line editor is a different story; we're talking about command lines being `exec`'ed here). When you `cat google`, `cat` doesn't autocorrect that to `googler`. You're responsible for what you type. If you made a typo, no sweat, do it again. (You can even correct the query right within googler's "shell", with all options preserved.)
Therefore, I propose to remove the `--exact` option and make it the default (that is, the only) behavior.
@jarun I'll raise a PR if you support this idea.
First,
```
$ brew unlink emacs
```
if you have emacs 25.1 installed.
Next,
```
$ brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/a03b944b96e79125fe06a37de41035e7df594e2e/Formula/emacs.rb
```
You might want to `install -s` to build from source if linkage of the bottle has been broken.
Later you can
```
$ brew switch emacs 25.1
```
if you still have the 25.1 keg and want to switch back to 25.1.
Note that you're on your own when you do this; you won't get support for emacs 24.5 here.
[ffmpeg] fix concat list when output dir is not pwd
===================================================
Relative paths in the concat list are considered relative to the parent directory of the script, not the calling directory. This isn't entirely obvious from the documentation, but it is easy to infer from the concat demuxer's concept of "safety", and easy to test (confirmed on FFmpeg 3.2.2). See https://ffmpeg.org/ffmpeg-all.html#concat-1 for details.
This commit fixes the wrong relative paths when `--output-dir` is specified and not pwd.
This commit also
- Factors out common concat list writer code;
- Slightly simplifies the code to collect FFmpeg params (on Py35+ we can further simplify by unpacking `LOGLEVEL` with the star operator right in the list literal).
<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/soimort/you-get/1558)
<!-- Reviewable:end -->
Caveats were never meant to replace or extend official docs (which is unfeasible to begin with; it's hard enough to maintain up-to-date documentation, not to mention *other people's* documentation), or be a getting started guide, or worse still, be a command line crash course.
> release notes
This has been discussed before, but the conclusion was it's pretty much impossible for us to do, because even when they're available, they come in all shapes and forms and styles and levels of verbosity.
> if they want that they need to go to the homepage.
They should.
Based on experience I don't think many people have complained about the lack of caveats.
Run
```zsh
for formula in "$(brew --repo homebrew/core)"/Formula/*.rb(:r:t); do caveats="$(brew info $formula | sed '1,/==> Caveats/d')"; [[ -n $caveats ]] && { print $'\e[32m'$formula$'\e[0m'; print -R $caveats; print }; done
```
in Zsh to get a feel for what actually belongs to caveats.