Excerpts from Jan Larres's message of Sat Sep 25 14:49:27 +0200 2010: > Dominique Pellé <[email protected]>: > At least for me the issue is not that the tag won't get found (if you look at > the tags file in my initial mail you'll see that the offending tag is not one > you would really want to search for), just that the error also prevents other > tags from being found if they come after this tag. Post-processing the tags > file like Marc suggests is of course possible, but it's a bit of a hassle > having to do this every time. So it would be nice if Vim could at least handle > it a bit more gracefully, even if just by ignoring the rest of a long tag.
parse_tag_line returns the failure on parsing. However to make it suceed on partial lines you still have to set filename and command. Setting it to NULL will result in the same failure (or would cause many changes + much testing) So the best solution which comes to my mind is keeping a static string "TAG_LINE_TOO_LONG_DOESN_T_FIT_INTO_BUFFER" and make the filename and the command point to it. Then when hitting that tag you'd open that buffer which at least gives some hinting about what goes wrong. In the usual case searching should continue without error (which is what we want) ? I may have missed some details. Is this worth fixing? If so would that fix be a bad hack only - or a reasonable tradeoff value vs effort ? I hit the same issue when tagging compressed .js files (which are in some of my repositories as well). So I'm interested in a fix as well. However its not worth spending hours on it. Marc Weber -- 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
