aboutsummaryrefslogtreecommitdiff
path: root/intl
diff options
context:
space:
mode:
authorMaciej W. Rozycki <macro@embecosm.com>2022-07-01 17:11:09 +0100
committerMaciej W. Rozycki <macro@embecosm.com>2022-07-01 17:11:09 +0100
commitc4de64f8f6df99078d55d329bed24bbe3b963aba (patch)
treec67a915a437751e9a68dfa065cf72e685712c143 /intl
parent1dd024239b551e55a867880d898a63fcf479b717 (diff)
downloadgdb-c4de64f8f6df99078d55d329bed24bbe3b963aba.zip
gdb-c4de64f8f6df99078d55d329bed24bbe3b963aba.tar.gz
gdb-c4de64f8f6df99078d55d329bed24bbe3b963aba.tar.bz2
GDB/doc: Remove extraneous spaces from completion examples
Completion results are usually different when the operation is applied to a word that is or is not followed by a space. In some cases they are equivalent, however a space would not be produced if completion was used earlier on in the word processed. However in the manual we have completion examples given using a space that actually prevents the example from working. E.g.: (gdb) info bre <TAB> (nothing) and: (gdb) info bre <TAB><TAB> Display all 200 possibilities? (y or n) as it now goes on to propose the entire symbol table, while: (gdb) info bre<TAB> (gdb) info breakpoints does the right thing, but is not what is shown in the manual. In other cases an extraneous space is used that does not correspond to the actual completion pattern shown, which gives an impression of sloppiness. Remove extraneous spaces then from completion examples as appropriate.
Diffstat (limited to 'intl')
0 files changed, 0 insertions, 0 deletions