Maxim Kim

Same happens with legacy blue in urxvt (copied into `~/.vim/colors/legblue.vim`, changed name to `legblue` inside colorscheme): With only `colo legblue` in `vimrc` and `$ vim`:  With only `colo legblue`...

And the difference between: `$ vim -Nu NONE +"colo legblue"` and `vim -Nu NONE --cmd "colo legblue"` ## `vim -Nu NONE --cmd "colo legblue"`  ## `$ vim -Nu NONE...

And it looks like normal highlight attributes are being ignored in urxvt and terminal.app: 1. `urxvt` 2. `vim -Nu NONE --cmd "colo blue" Makefile` 3. `:hi normal` You can see...

1. Try without colorscheme 2. Try without `syntax enable` 3. Try with different terminal (iterm2?) If possible provide your repro steps in textual format. Regarding ssh to a different machine,...

This is the same issue @neutaaaaan was about in https://github.com/vim/vim/issues/11177 As of now only 2 terminals are known to be affected, urxvt and Terminal.app Not sure if this is vim...

Well, I am wrong, this is a different issue. And affects all terminals.

Hi @mogest , indeed, @mojavelinux explained it to me. Too bad inksape does simple gradients in unsupported way, but well, that is life :) Thank you!

> > Could you explain in more detail why these approaches don't work for you? What about windows? Main issue that there is no xargs. And if you try to...

Yes I understand it might be not that trivial to implement. But it would be really convenient. My current setup is 'fuzzy' but quite often I remember parts of the...

@abo-abo Just have tried swiper-all --- and it doens't work at the moment. ``` Error in post-command-hook (ivy--exhibit): (wrong-type-argument characterp ("s" . t)) ```