On 02-Apr-2013 glts <[email protected]> wrote: > On Tue, Apr 2, 2013 at 1:59 AM, Lech Lorens <[email protected]> wrote: > > On 01-Apr-2013 Bram Moolenaar <[email protected]> wrote: > >> How about this alternative: Filter your tags file to change the patterns > >> to include an optional CR before the $: \r\=$ > > > > This is something I would prefer to avoid. My current situation is that > > to prepare a tags file I process a few millions lines of code (this is > > after filtering only the relevant parts from about 80 millions LOC) and > > it takes ages to run ctags and cscope. I would rather not cause this > > step to take longer and would prefer a 200 ms search instead of a 100 ms > > one whenever I execute ":tag foo". > > I understood Bram's suggestion to mean you could postprocess your tags > file, after it has been generated. This would be fast, no matter the > size of your codebase. For example for Exuberant ctags: > > /^\([^\t]\+\t[^\t]\+\t[^\t]\+\)\(\$\%[/;"].*\) > :%s//\1\\r\\=\2/ > > I feel this is a situation where a few lines of shell or Vim script > would be most appropriate.
Vim takes about 20 seconds to fix my 200 MB tags file. Perl takes about 6 seconds. That's still ages on an AFAICT high-end Core i7. Too long for my taste – I'll stick with my patched Vim. I wonder however, if all the people that tried Vim and decided it was not suitable for the task tried the simple and obvious most appropriate one-liner before giving up and choosing an editor that just worked. -- Lech Lorens -- -- 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.
