Max Odnoletkov

> 1. Explicitly extract these set of keys, e.g.: { a: .a, c: .c } You can use shortcut syntax here – just `{a, c}`. But it won't work for...

BTW in Vimium there is even more advanced feature for this – [filtered hints](https://github.com/philc/vimium/wiki/Using-Link-Hints#filtered-hints). Instead of using full-text search to target links (which is sometimes inconvinient because it would hit...

> `/dev/stdin` on linux is a link to `/proc/self/fd/0` which only is a valid link if the file is named (including some devices, like pseudo-terminals). @bfredl thanks for the explanation,...

Isn't that too broad of a task for this utility? You may also want to resolve the same problem for other history rewriting, not only for git-revise – for the...

> How would `git with-updating-refs` possibly work? There's no way for it to figure out what new ref the old ref maps to unless it's involved in the rewriting (even...

I use `git absorb && git revise --autosquash` all the time – I don't see how this can be improved

FWIW `:Gclog -g stash` loads all stashes to the quickfix list. You can then browse them and apply using `czapply`

@matochondrion `cza` always applies topmost stash ('count' stash actually) – and I want to apply currently selected stash

There is also cF and cS – any reason to skip them?

A few things I don't like: * The logic deciding which side to pick for the path is hardcoded in vim-fugitive. It matches what Github and Bitbucket currently use but...