diff options
| author | Maciej W. Rozycki <macro@embecosm.com> | 2022-07-01 17:11:09 +0100 |
|---|---|---|
| committer | Maciej W. Rozycki <macro@embecosm.com> | 2022-07-01 17:11:09 +0100 |
| commit | c4de64f8f6df99078d55d329bed24bbe3b963aba (patch) | |
| tree | c67a915a437751e9a68dfa065cf72e685712c143 /gdb/doc | |
| parent | 1dd024239b551e55a867880d898a63fcf479b717 (diff) | |
| download | gdb-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 'gdb/doc')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f7b02c2..ad5bc7d 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -1915,7 +1915,7 @@ enter it). For example, if you type @c If texinfo enhancements make it unnecessary, it would be nice to @c replace " @key" by "@key" in the following... @smallexample -(@value{GDBP}) info bre @key{TAB} +(@value{GDBP}) info bre@key{TAB} @end smallexample @noindent @@ -1945,7 +1945,7 @@ function names in your program that begin with those characters, for example: @smallexample -(@value{GDBP}) b make_ @key{TAB} +(@value{GDBP}) b make_@key{TAB} @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see: make_a_section_from_file make_environ make_abs_section make_function_type @@ -2039,7 +2039,7 @@ the word-completion facilities in this situation, type a single quote when you press @key{TAB} or @kbd{M-?} to request word completion: @smallexample -(@value{GDBP}) p 'func< @kbd{M-?} +(@value{GDBP}) p 'func<@kbd{M-?} func<int>() func<float>() (@value{GDBP}) p 'func< @end smallexample @@ -2050,7 +2050,7 @@ usually need to type a quote before the function name, because function: @smallexample -(@value{GDBP}) b func< @kbd{M-?} +(@value{GDBP}) b func<@kbd{M-?} func<int>() func<float>() (@value{GDBP}) b func< @end smallexample @@ -2063,9 +2063,9 @@ that takes an @code{int} parameter, @code{name(int)}, or the version that takes a @code{float} parameter, @code{name(float)}. @smallexample -(@value{GDBP}) b bubble( @kbd{M-?} +(@value{GDBP}) b bubble(@kbd{M-?} bubble(int) bubble(double) -(@value{GDBP}) b bubble(dou @kbd{M-?} +(@value{GDBP}) b bubble(dou@kbd{M-?} bubble(double) @end smallexample |