Tim Pope

You could probably stick options in `g:fugitive_git_executable`. But you don't need that for this: Set `color.ui` to `auto` and Git will only use color when connected to a terminal.

Also note that we *do* [force the color options to `false`](https://github.com/tpope/vim-fugitive/blob/46eaf8918b347906789df296143117774e827616/autoload/fugitive.vim#L3732-L3735) in most invocations of `git`, because `color.ui=always` is a common mistake. What command is giving you color escape escape...

> I get the color escape sequences when I push. When I push, there's a link to create a PR. This link is colored. I'd like it to not be....

Basically, you need to make your `:Gstashes` command edit some made-up path (`fugitive:///path/to/repo/.git//stashes` would be consistent with the rest of fugitive), and then implement a `BufReadCmd` to fill in that...

This is certainly on the todo list for the new `:Gstatus`. Displaying a list of stashes and providing maps to pop/apply/drop is relatively straightforward. The annoying part is displaying the...

> Displaying a list of stashes and providing maps to pop/apply/drop is relatively straightforward. As hinted at above, the design here is now complicated by the fact we now have...

This isn't a backwards compatibility concern. I want there to be a no-brainer map that pops the topmost stash, as that's what you want to do 99% of the time.

I'm leaning strongly in the direction of overloading the other context sensitive maps: `X` could be `drop`, naturally, and we could stick `pop` on `u` or something? The tricky part...

`git stash pop` won't drop the stash if there are merge conflicts. I do think the operation is a bit too aggressive to trigger on a single key press, and...

I never merged this because I was extremely unsatisfied with the color distribution. Six of the 16 colors will only be used if you have code that is older than...