Closed woshilapin closed 11 years ago
Some other problems seems to make me think that this is a Vim problem and not a vim-autotags
plugin problem. In fact, if I source
(the vim macro) a file in this same broken directory, I have the same error on the line where the source
macro is called. So I tried to move the all directory in a more simple directory name (without space) and it seems to work.
This problem is a mistery, why vim has problem on some weird path and has no problem on simpler or weirder path?
However, I close this ticket because it seems to be independent of the vim-autotags
project.
When open a new file in a specific condition (not yet identified but some details below), I get the following error:
I tried to identify the problem and the error is done by the
findfile()
function. However, in most of my directories, I have not this problem.Firstly, I suspect that the current absolute path has a weird character (like a space or an accentuated character): my current directory only has a few spaces in it. Moreover, I succeed in opening a file in a weirder directory (spaces and accentuated characters).
Secondly, I suspected a weird filetype where other vim plugin are loaded and interfere with
vim-autotags
. But I tested a few different extension in this broken directory with always the same result. However, in sane directories, no problem with the same directories.Thirdly, I suspected a previous generation of
tags
orcscope.out
file (even if I don't need them in this broken directory) then I cleaned my.autotags/byhash/
directory. Unsuccessful.My vim version is here.
I have no
tags
orcscope.out
(or other cscope files) in the directory, in all the parent directories or subdirectories (indeed, there is not subdirectories).The last detail that may be the cause of the problem is that the directory is in a Dropbox directory. However, all the test I previously explained have been made on Dropbox too: I have sane directories AND broken directories in Dropbox.