Roy Orbitson

Using this now so each invocation gets all arguments, rather than each argument being a separate script, like @ttimasdf's but using a plain array: ```vbscript Dim args() Redim args(Wscript.Arguments.Count -...

@hackedWifi It does belong here. This theme currently limits the palette to 16 colours for any terminal not capable of true colour, rather than detect 256 colour mode (`:set t_Co?`)...

@hackedWifi I don't know why you're getting so worked up about this. Picking some close colours so the theme is legible, out of the box, is not a terrible idea....

[Forked it.](https://github.com/Roy-Orbison/nord-vim-256)  I'm sure I made mistakes so feel free to submit pull requests to correct them.

I don't know for sure that the `/` is the cause, but removing the branch specifier allows the installation without error. BTW, my Git is version 1.8.3.1.

The answer is in the bug report, I just didn't realise. It's not the branch name. I tried with this entry: ```viml Plug 'joonty/vim-taggatron', {'branch': 'python3'} ``` It failed again....

It wasn't that simple, either. This works: ```sh git checkout -q --track origin/python3 -- 2>&1 ``` When installing a plugin, I think it should be explicit about tracking the remote...

Can we just add a check to see whether the local branch exists, and if not, add the `--track` flag to this command? https://github.com/junegunn/vim-plug/blob/8b45742540f92ba902c97ad1d3d8862ba3305438/plug.vim#L1297

This patch solves the initial install for me, I'll let you know how updates go. It puts the plugin repo into a detached HEAD state like the tag option. ```patch...

Same. Re-authenticating with the following did not help: ```sh maestral auth link --relink ```