*Remote* branch name must be listed along with 'PUSH' keyword.

This requires predictable name of the remote, but as this whole slurping
thing is only meant for very dirty, very local scenarios, that should
not be problem.  (Other, more open scenarios are still possible, just
harder, as they probably should be.)

Using grep directly could result in "binary file matches" without any
useful info.

This would happen e.g. after renaming some files with badly-encoded
filenames.  Bash history builtin seems to address such cases better.

(Return cursor after pasting; not sure how well it works for lines but
it's ok for chars.)

In that case (i.e. , the `${full#git_root}` would not work and print the full
basically full absolute path to git root.

Use "meta templates" that ate actually Bash scripts.

 *  Add --force-* options to skipt .git-slurp-ok file checks.

 *  Allow passing path to slurp.

    You can slurp only a particular sub-tree.

 *  Improve commit message.

    Host has been dropped, and slurped paths are logged (as relative
    to worktree root).

Makes more sense to have darker cursor when "inside" in insert mode.

Apparently with some distros, raching 0 will turn off the display
completely.  Step of 49 makes it easy to avoid that while still keeping
the advantage of huge step.

 *  Die by dedicated function.

 *  Push only if allowed (a line containing single word PUSH found in
    .git-slurp-ok file)

 *  Allow working when deeper in git repo (but not if outside).

 *  Make permisson code readable (self-doc).

 *  Enclose in main() to allow for better hygiene.

Now host/user overrides don't have to be created.

Useful in repos with more users and especially in those with abundance
of tags.

Note to self: TODO: merge with other modes

Current bmo development version uses *first* reciord as default (which
seems to make more sense)

Goodbye mocp :'), hello clementine... :)

Albeit a bit hidden, Orage does have a setting to start minimized, so
it's not necessary to toggle it after start.

They are already contained within the fetched string.

These variables only make sense in interactive bash session where we
always re-read .bashrc anyway.