On Wed, June 5, 2013 00:14, Tony Mechelynck wrote: > On 31/05/13 15:31, A. S. Budden wrote: >>> When using cscope, the path as provided to the "cs add" command is >>> used. If the working directory changes, this is potentially no longer >>> valid. This causes me a problem as I have a plugin that tries to >>> pause cscope and restart it (so it can regenerate cscope.out without >>> access conflicts). It does this by parsing "cs show" to get the file >>> name(s) and then doing "cs kill" to pause and "cs add" to restart. If >>> the working directory has changed, "cs add" fails. > > IIUC, the solution to this is to provide as an optional argument to the > ":cs add" command the path from which cscope.out was generated, e.g. as > follows:
No, this is a different problem, as explained by Gary here: http://article.gmane.org/gmane.editors.vim.devel/39984 regards, Christian -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
