aboutsummaryrefslogtreecommitdiff
path: root/gdb/target-descriptions.c
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2023-02-13 16:14:55 +0000
committerPedro Alves <pedro@palves.net>2023-02-15 15:28:33 +0000
commit71e28f788f4e5489501646093c6a34e01681d35b (patch)
tree1cf1c62d781ce1ae95315c5195009bc67b69d54c /gdb/target-descriptions.c
parentf9c36cc99518c74a0562e86e1e27ec46cf57d49a (diff)
downloadbinutils-71e28f788f4e5489501646093c6a34e01681d35b.zip
binutils-71e28f788f4e5489501646093c6a34e01681d35b.tar.gz
binutils-71e28f788f4e5489501646093c6a34e01681d35b.tar.bz2
gdb/manual: Move @findex entries
The manual currently has many cases like these: @item $_gdb_setting_str (@var{setting}) @findex $_gdb_setting_str@r{, convenience function} As suggested by Eli, move the @findex entries before @item so that the index records the position of @item, and the Info reader places you there when you use index-search. I went over all @findex calls in the manual, and most are like the above. Most either appear before @item, or before @subheading, like: @subheading The @code{-break-after} Command @findex -break-after I fixed all of them. There are findex entries in annotate.texinfo,python.texi, and stabs.texinfo as well, though those all look right to me already. Tested by typing "i _isvoid" (@item case) and "i -complete" (@subheading case) in an Info reader, and checking where those took me. Change-Id: Idb6903b0bb39ff03f93524628dcef86b5585c97e Suggested-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/target-descriptions.c')
0 files changed, 0 insertions, 0 deletions