vim-fetch
vim-fetch copied to clipboard
wsdjeg
Make Vim handle line and column numbers in file names with a minimum of fuss
With https://github.com/zhimsel/vim-stay installed, `vim dist/index.js:155:9` will open `dist/index.js`, but at the beginning of the file. `vim dist` and then running `:e index.js:155:9` also doesn't work as expected - we open...
The tagbar will auto open with "autocmd FileType * call tagbar#autoopen(1)", when open whith "vim include/linux/locallock.h:233:3" the curser will goto tarbar window. 
``` ~/src/k8s.io/ingress-nginx/internal/ingress/controller/nginx.go:665 ``` If cursor is on the 665, we cannot jump to the file with error ``` E447: Can't find file "665" in path ``` It would be much...
is it intentional that sourceing v3.0.0 vimball creates the files under `~/.vim/Users/martin` ? (I'm Using Windows , WSL, vim 8.0)
Is it possible to add support for (filename.ext,177|28) type of error logs? This line means, we should be able to go to line 177 and column 28.
In this case `nvim src/lib.rs:121:23` broke everything, but `nvim src/lib.rs:121:23:` and `nvim src/lib.rs:121:22` worked. Sometimes the trailing colon causes breaks to. The files are standard UTF-8 ASCII characters only. 
Using the default vim-fetch settings, `gF` on `foo.py:46:` in the following text fails for me (Vim 7.4.618): ``` foo.py:46: if(not Directory.Exists(destinationDir)): foo.py:49: if(File.Exists(filePath)): foo.py:54: if not Directory.Exists(self.PATH_TO_FILES): ``` Error: ```...
I've thought to use this plugin to get the filename under the cursor in a quickfix list, and then `:edit` it after `wincmd w`. From a quick glance `fetch#cfile` does...
I've just remembered that I have the following in my vimrc: ``` au BufNewFile * nested let s:fn = expand('') | \ if ! filereadable(s:fn) | let s:fn = substitute(s:fn,...