Terminal emulator: alacritty 0.11.0 (also tried with kitty and got same behavior)
ranger version: ranger 1.9.3
Python version: 3.10.8 (main, Nov 1 2022, 14:18:21) [GCC 12.2.0]
Locale: ru_RU.UTF-8
Current Behavior
set colorscheme command does not work properly. It changes colorschme only partially. I created two simple colorschemes, for which method use() return either (0,0,normal) (zenlight) or (255, 255, normal) (zendark). After running ranger with the light colorscheme I get (as excepted):
But after execution `set colorscheme darktest, I get:
It seems that ranger applies colorscheme only in directories that were not visited before setting a new colorscheme (here I switched to some random directory):
This work with default colorschemes too. Also, I tested this in kitty and noticed the same thing.
Expected Behavior
Running with darktest colorscheme gives
So getting this after running set colorscheme zendark is (I think) expected behavior.
Yeah, this is a known bug. Thanks for the report though. Kinda has a low priority for us since changing the colorscheme while running Ranger doesn't occur that often. PRs welcome though : )
Runtime Environment
Current Behavior
set colorscheme
command does not work properly. It changes colorschme only partially. I created two simple colorschemes, for which methoduse()
return either(0,0,normal)
(zenlight) or(255, 255, normal)
(zendark). After running ranger with the light colorscheme I get (as excepted):But after execution
`set colorscheme darktest
, I get:It seems that ranger applies colorscheme only in directories that were not visited before setting a new colorscheme (here I switched to some random directory):
This work with default colorschemes too. Also, I tested this in kitty and noticed the same thing.
Expected Behavior
Running with darktest colorscheme gives
So getting this after running
set colorscheme zendark
is (I think) expected behavior.Steps to reproduce