find text has one issue for linux kernel code with "tab"
Solved on the VIM end of things (as of v9.2.1259)
find text has one issue for linux kernel code with "tab"
"cs find" is not exactly a cscope command. It's a vim integration command. Which means, given that cscope itself appears to quite successfully display those lines, if run by itself, the responsibility for the garbled display would IMHO have to be laid at the feet of the VIM integration for cscope.
The report is a bit unclear on what, exactly, you asked cscope to do, and what you were using to look at its output. Which -L mode client was that, and why woud its potential failure to cope with tab characters, which are perfectly fine in C source code, have to be seen as cscope's problem? The way the output was mangled by SF's markdown processing also makes it quite hard to judge what might be wrong here. I'm pretty sure there were not two <unknown> tags in cscope's actual output. It also doesn't...
The report is a bit unclear on what, exactly, you asked cscope to do, and what you were using to look at its output. Which -L mode client was that, and why woud its potential failure to cope with tab characters, which are perfectly fine in C source code, have to be seen as cscope's problem? The way the output was mangled by SF's markdown processing, making also makes it quite hard to judge what might be wrong here. I'm pretty sure there were not two <unknown> tags in cscope's actual output. It also...
Hmmm... checked out git current source straight from their original upstream. Class 1: No two-line function definition for radius_das_disconnect matching your description seems to exist in there. The definition has looked like this, for the last 14 years and counting: static struct radius_msg * radius_das_disconnect(struct radius_das_data *das, struct radius_msg *msg, const char *abuf, int from_port) What gives? The issue itself does exist, and is most likely an instance of the well-known and documented...
noautititle, notitle and empty title