Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.

How to get history working in bash on windows

0 votes
asked Feb 8 in vifm by Dan Osborne

I've installed vifm in bash on ubuntu on windows using

apt-get install vifm

and am pleased to see that it basically works but there seems to be no command history

There is no .vifm/vifminfo file created (though there is a vifmrc, Trash etc).

The output from vifm --version is...
vifm 0.4

Do I need a later version perhaps?



1 Answer

+1 vote
answered Feb 9 by xaizek
selected Feb 10 by Dan Osborne
Best answer

Do I need a later version perhaps?

Yes, definitely. v0.4 is very old, buggy, lacks many things and configuration is completely different there.

If that's all they have, you might need to build vifm from source package. Instructions are here. You'll need a build tools though, like gcc, I think there was a package like "build-essentials" to install them.

commented Feb 16 by Dan Osborne
edited Feb 16 by xaizek

Ah sorry, :nmap outputs "go to item below"

and locale says...

commented Feb 16 by xaizek

OK, I reproduced it. Looks like it happens for me only if I open cmd window and start bash from there and do not change focus on another window (all of this is weird).

I'm bisecting to see what might be the cause, but for now try starting bash in some different way. And I get wrong box characters for fixed font, but all is fine for couriel new or consolas.

commented Feb 17 by xaizek

There is line 178 at src/ui/ui.c:


Replace 0 with 5, this should fix it.

It works as is on most systems because they insert all bytes atomically, apparently it's not the case here. Generally speaking the delay might be useful on other systems in corner cases as well and shouldn't be noticeable, so I'll probably make this change for all systems.

commented Feb 20 by Dan Osborne

Well, bash on windows was bound to be weird! My prompt was run from the standard icon that has target: C:\Windows\System32\bash.exe ~

However, I did an apt-get upgrade before getting your latest reply and this seems to have sorted it. It upgraded these packages...
bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), libdns100:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), libisccfg90:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), libbind9-90:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), dnsutils:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), libisccc90:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12), libisc95:amd64 (9.9.5.dfsg-3ubuntu0.11, 9.9.5.dfsg-3ubuntu0.12)

I've made your code change and re-built for completeness but my suspicion is that bash on ubuntu on windows is a little flaky,

Thanks for investigating,


commented Feb 20 by xaizek

There is more to its weirdness. After it starts working (also happens if you run another application, not just vifm), it works until you restart the bash. This might explain how upgrading "fixed" it.

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here won't be considered as spam, but this is not a perfect place for it.