bwpge

I would really love to have this feature. I am used to having my branch background color red if dirty or yellow if in a modified state (among other color/logic)....

This doesn't solve your ask for plugin descriptions on hover, but [`gx.nvim`](https://github.com/chrishrb/gx.nvim) can open plugin pages from repo shorthands like `foo/bar`.

Ah Windows paths, the gift that keeps on giving 😂 @pysan3 I will take a look in the morning

For anyone who wants to take a look in the meantime, my best initial guess is we'll probably just have to add braces to this escape logic (totally guessing though):...

Reproduced the issue on my machine, looks like somewhere the parenthesis is not getting escaped (trying to open `baz.txt` or `other.txt`): ``` [Neo-tree ERROR] X:\test\[foo](bar) : ENOENT: no such file...

After doing some testing, it seems specifically the `[foo]` (square bracket) segment followed by `(bar)` (parenthesized) segment causes this super odd problem. I can't even directly open the file by...

The `/` separator actually goes back to my original contribution to Neo-tree, unfortunately this causes problems with other plugins (see: https://github.com/nvim-lualine/lualine.nvim/issues/1183 for example). I know it's not Neo-tree's responsibility to...

On the bright side, this is what I'm testing now and seems to be working for weird paths, including something like `X:\[foo]\(bar)\&baz.txt` (I found `(bar)\\&baz.txt` has the same problem with...

Just wanted to check in, haven't forgotten about this issue just had a crazy schedule this week. Hope to get a PR sent in tonight or tomorrow night.

From some more testing, I've come to the conclusion that a square bracket or backtick in the path makes other problematic punctuation (the ones we discovered like `&`, `^`, etc.)...