aboutsummaryrefslogtreecommitdiff
path: root/gdb/utils.c
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2021-01-22 10:06:17 +0000
committerAndrew Burgess <andrew.burgess@embecosm.com>2021-01-22 18:34:31 +0000
commitd8c4766d31456946a2a42239bccc789af3eaa1b9 (patch)
treec320da0a6e19e7b7d28569388ac237728de812cd /gdb/utils.c
parent2189c312652ae4f66eaf55b306cb64d4c1678636 (diff)
downloadgdb-d8c4766d31456946a2a42239bccc789af3eaa1b9.zip
gdb-d8c4766d31456946a2a42239bccc789af3eaa1b9.tar.gz
gdb-d8c4766d31456946a2a42239bccc789af3eaa1b9.tar.bz2
gdb/doc: don't rely on @menu item within the docs
The node 'Auto-loading extensions' currently relies on a @menu item to provide a set of cross-references to different parts of the manual. Additionally the menu is placed part way through the node and the text prior to the menu seems (to me) to assume that the menu will be formatted into the document. This is a bad idea as the menus are not always part of the final document (e.g. pdf output does not include the menu), when compared to the info page the pdf version of this node is less helpful as it lacks proper cross references. Menus should always be placed at the end of a node. In this commit I rewrite a paragraph to add extra cross references inline within the text. I then move the menu to the end of the node. gdb/doc/ChangeLog: * gdb.texinfo (Auto-loading extensions): Add additional cross references and move @menu to the end of the node.
Diffstat (limited to 'gdb/utils.c')
0 files changed, 0 insertions, 0 deletions