xaizek
xaizek
> Could this be related to Alacritty's colorscheme somehow messing with this? Unlikely, it would show up in both panes, you can try `xterm` or whatever other terminal is installed...
Have you tried other terminals just in case? I tried installing `alacritty` using `nix`, but it won't start. You can try running `:highlight OtherWin ctermfg=default ctermbg=default` after `:highlight clear` to...
Thanks. Those are basically first and last commands of `Default.vifm`. Please try commenting out the rest of the file and see if the issue persists. If it doesn't appear, try...
Using your configuration doesn't trigger it either... That `OneDark.vifm` doesn't have `OtherWin`, maybe try adding ```vim highlight OtherWin ctermfg=default ctermbg=default ``` or ```vim highlight OtherWin cterm=none ctermfg=default ctermbg=default ``` It...
Is it only Vim that's messed up or Vifm too? It's not entirely clear from the video. In this case terminal, the way it's started (number of resizes), Vifm and...
`$LINES` and `$COLUMNS` can be the reason, thanks @Tokariew. Curses can use them and might even update, hiding incorrect initial values (although I'm not sure why they would cause much...
Use quotes or backslashes to escape spaces: ```vim set vicmd='sleep 0.1 && nvim' ```
Hello, > Global vs pane tabs scope This made me realize that if your current pane tab has a name, you don't get too see path at all. > Uniquify...
You could start it like this (Vifm will be "frozen" until the viewer ends): ```vim command! viewimage :execute 'goto' fnameescape(system(expand('viewer %c'))) ``` A more transparent, but also more complicated way...
Yes, menus don't process escape sequences. View mode does and maybe that code can be used in menus too, but not sure how much effort it would take to integrate...