diff options
author | Kaz Kylheku <kaz@kylheku.com> | 2020-09-01 06:51:35 -0700 |
---|---|---|
committer | Kaz Kylheku <kaz@kylheku.com> | 2020-09-01 06:51:35 -0700 |
commit | 0f6702adbc7792499fba6d2fb067fb817a603fd6 (patch) | |
tree | 5772125bff66a9351b453204b0228d6d83fc3e24 /share | |
parent | 286bb507a316acefcecc87865f3a152c403ea8b3 (diff) | |
download | txr-0f6702adbc7792499fba6d2fb067fb817a603fd6.tar.gz txr-0f6702adbc7792499fba6d2fb067fb817a603fd6.tar.bz2 txr-0f6702adbc7792499fba6d2fb067fb817a603fd6.zip |
tags: address small issue with tag lookup.
Exuberant Ctags uses the full content of one line as the key
to find a tag. A function declaration that is split into
multiple lines can have a first line which is identical to the
definition, as in:
static int add(int a,
int b);
static int add(int a,
int b)
{
return a + b;
}
Here, the search key which ctags uses for the add function is
"static int add(int a,", taken from the definition. But it's
exactly the same as a the first line of the declaration, and
that is what Vim jumps to for that tag.
A few function declarations in TXR have this issue.
* eval.c (expand_params_rec, do_eval): Make the first line of
the forward declaration different from the first line of the
definition.
* match.c (mf_all): Likewise.
* struct.c (make_struct_type_compat): Likewise.
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions