nacitar / a.vim Goto Github PK

Using a.vim from commit f3cfbbf:

Steps to Reproduce

• Create the following directory structure (files can be empty or contain placeholder content):

    bugtest/AlphaBeta.h
    bugtest/Beta.cpp
    bugtest/include/Beta.h
  

• Edit all files:

    mvim bugtest/AlphaBeta.h bugtest/Beta.cpp bugtest/include/Beta.h
  

• :n to advance to Beta.cpp.

• :A should open Beta.h but instead opens a new file (buffer) Beta.h in the same directory as Beta.cpp.

• If AlphaBeta.h were removed, or renamed to AlphaGamma.h, then :A works fine on Beta.cpp → Beta.h.

• It seems that :A on Beta.cpp cannot decide between include/Beta.h and AlphaBeta.h and so it chooses neither.

  • In such a case, a filename match (regardless of directory path) should be selected over a string prefix match.

Since this is an improved version of a.vim, could you update the readme to note that?

I've noticed that sometimes the plugin opens the incorrect alternate file.
This behavior can be very annoying if it is perceived after a long time
editing the wrong file.

The problem can be reproduced with the following directory hierarchy:

Base folder/
| New folder Copy/
| | TeSt.h
| | TeSt.c
| New folder/
| | test.h
| | test.c

It also happens when "New folder" and "New folder Copy" are in completely
unrelated folders. It seems that the only condition needed is that two files
with whose filenames are equal in a case insensitive comparison are open.

To reproduce the fault:

1. Open TeSt.c and split open test.c
2. use :ls to check that there are only two buffers open
3. execute :A with the focus on window displaying TeSt.c and notice that
   test.h is displayed instead of TeSt.h

The problem disappears if file TeSt.h is already loaded:

4. <c-o> to return to TeSt.c
5. :e TeSt.h
6. <c-o> to return to TeSt.c
7. execute :A and notice that now TeSt.h is displayed

Any ideas?