Comments
-
Greg Hurrell
Relative to what, exactly? Vim already uses relative paths for buffers, and Command-T uses the paths that Vim provides.
-
anonymous
Well, when I do :pwd in Vim, I can see that I'm in C:\Users\oskarkv\Desktop\spelet. And when I do :CommandTBuffer, the buffers are listed like this:
C:\Users\oskarkv\Desktop\spelet\src\game\client\core.clj C:\Users\oskarkv\Desktop\spelet\src\game\server\core.clj C:\Users\oskarkv\Desktop\spelet\src\game\networking\core.clj C:\Users\oskarkv\Desktop\spelet\src\game\utils.clj
etc.
But in :CommandT, the C:\Users\oskarkv\Desktop\spelet prefix is gone. I would like :CommandTBuffer to work the same way. But you said Command-T uses what Vim provides, so maybe the problem is not with Command-T. Hm...
-
Greg Hurrell
Not entirely sure if the behavior on Windows is the same as on UNIX, but you can look at the buffer listing as provided by Vim with
:ls
.At least on UNIX, that always uses relative paths. Command-T isn't literally using the output of
:ls
(it's actually using the Ruby API) but on UNIX the returned strings are the same. -
anonymous
Created
,
edited
:ls
returns1 h "dev\user.clj" line 50 2 a "[Scratch]" line 0 4 h + "src\game\server\core.clj" line 60 5 [/tags/a #a] + "src\game\client\core.clj" line 73 6 h "todo.txt" line 69 15 %a "\Program Files (x86)\Vim\_vimrc" line 36
So I guess the Ruby API does not return the same then. Maybe the Ruby code can check that somehow and strip the prefix?
Add a comment
Comments are now closed for this issue.