xaizek

Looks like the answer is negative at the moment. Those Unicode chars are too new and their width isn't determined correctly (might require newer `libc`). Curses has pseudo-graphics in its...

It can't be disabled. Why do you want to disable it? Prior to introduction of the message it used to quit. Size limit can't be disabled completely because at some...

Before it becomes text in the terminal, it's a set of curses windows. `wresize()` of curses fails if you set window height/width to zero and weird things follow, that's why...

> or content (size + hash) I'll update this, current wording can suggest that file equality might be a false positive due to hash collisions or that whole file is...

Those kind of things can't be optimized much. Confirming file equality will take reading it, which is slow (a handful of relatively large files and lots of small files are...

What's your version of vifm.vim and are there any settings for it? The latest version will use `:terminal` inside gvim when it's available. Otherwise a terminal will be used instead...

> Undefined variable: b:data This is more of a symptom as well (although this could be handled better), `term_start()` fails fast and calls calllback before `b:data` is set. What's interesting...

You mean something like this? :)  > there is a hardcoded number of things which could be highlighted differently That's list of predefined color groups, file-specific highlighting is in...

> How hard would it be to implement matching by modification time? Not terribly hard I guess. Things to do would be: 1. Pick syntax (borrowing part of `mutt`'s syntax...

I actually have an old branch (almost exactly 8 years old) with error dialog displayed on command-line and I think the idea was to make it more Vim-like. I might...