After some time, vim stops responding to any actions. The console emulator is responsive. This is definitely not Ctrl+s - Ctrl+q joke and not a layout. Sometimes does not respond to SIGHUP . After a successful SIGHUP says:

 Vim: Finished. Hangup

After kill -9 , several commands entered in the “embarrassing” state are displayed in the console (move, ex-commands).

 kkjjjkk:q

Restarting vim does not fix the problem. Restarting the system for a short time is also a random variable.

What could be the problem? No plugins installed (just before this).

UPD .

It seems that uncommenting lines in ~/vimrc helped:

 map <C-\> :tab split<CR>:exec("tag ".expand("<cword>"))<CR> map <A-]> :vsp <CR>:exec("tag ".expand("<cword>"))<CR>

But I'll never know why?

UPD2 .

Apparently, editing vimrc indirectly somehow eliminated or obscured the problem. There is no composition of the problem and the way to study it

UPD3 .

After a while, the error returned (with the old vimrc). Without it, vim works correctly (see the -u flag). Strace showed that (unlike normal operation) there is an unsuccessful call to ~/vimbak/.swpx . Created it while the flight is normal.

  • one
    run vim -u some_non_exists_file in the mode of configuring the configuration ( vim -u some_non_exists_file and check if the problem repeats. If not, the problem is in the config. If yes, the problem is deeper. - KoVadim
  • @KoVadim, thanks, good recipe. But after editing the configuration file, the error disappeared as unexpectedly as it appeared. Even with newly commented lines, it did not appear. - LXA
  • @KoVadim, the method you suggested yielded results! This is some kind of incorrect config. - LXA

1 answer 1

Of course, if the problem is not reproduced, then we can only guess about its causes.

but maybe someone else might experience similar symptoms, because a couple of recommendations:

  1. To find out if a program’s configuration is causing a problem, you can call a program with the -u NONE option (see :help -u for details). this will not load any configuration files and plugins.

  2. to find out whether the manifestation of a problem with disk operations, in the operating system gnu / linux (and, apparently , in * bsd ), you can use this, for example, the command:

     $ strace -f -e open -o /tmp/какой-нибудь-файл vim

    attempts to open files will be recorded in /tmp/какой-нибудь-файл file.

    in osx there is an approximate analogue - dtruss (see 1 and 2 ), which, apparently, is called something like this:

     $ dtruss -f -t open vim 2>/tmp/какой-нибудь-файл