Benjamin Fritz wrote:
The attached test_vimrc.vim sets up a command that (on Windows)
generates a tags file asynchronously and then calls back into Vim using
--remote-expr to add that tags file to the 'tags' option.
The test_vimrc.vim also sets the 'cscopetag' option to enable selecting
On Mon, May 4, 2015 at 1:05 PM, Bram Moolenaar b...@moolenaar.net wrote:
Benjamin Fritz wrote:
The attached test_vimrc.vim sets up a command that (on Windows)
generates a tags file asynchronously and then calls back into Vim using
--remote-expr to add that tags file to the 'tags'
Benjamin Fritz wrote:
The attached test_vimrc.vim sets up a command that (on Windows)
generates a tags file asynchronously and then calls back into Vim using
--remote-expr to add that tags file to the 'tags' option.
The test_vimrc.vim also sets the 'cscopetag' option to enable
Hi Ben!
On Fr, 20 Mär 2015, Ben Fritz wrote:
On Friday, March 20, 2015 at 8:39:19 PM UTC-5, Ben Fritz wrote:
On Friday, March 20, 2015 at 7:00:21 AM UTC-5, Bram Moolenaar wrote:
Are you able to get a stack trace of the crash? Or even better, have it
crash in a debugger?
On Friday, March 20, 2015 at 8:39:19 PM UTC-5, Ben Fritz wrote:
On Friday, March 20, 2015 at 7:00:21 AM UTC-5, Bram Moolenaar wrote:
Are you able to get a stack trace of the crash? Or even better, have it
crash in a debugger?
Sure will!
...as soon as I can figure out how to force
On Friday, March 20, 2015 at 7:00:21 AM UTC-5, Bram Moolenaar wrote:
Are you able to get a stack trace of the crash? Or even better, have it
crash in a debugger?
Sure will!
...as soon as I can figure out how to force ctags to parse those stupid *.pro
files along with the rest of the code.
Benjamin Fritz wrote:
The attached test_vimrc.vim sets up a command that (on Windows)
generates a tags file asynchronously and then calls back into Vim using
--remote-expr to add that tags file to the 'tags' option.
The test_vimrc.vim also sets the 'cscopetag' option to enable selecting
