From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1256) id 34C9F385E013; Fri, 1 Jul 2022 16:12:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 34C9F385E013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Maciej W. Rozycki To: gdb-cvs@sourceware.org Subject: [binutils-gdb] GDB/doc: Remove extraneous spaces from completion examples X-Act-Checkin: binutils-gdb X-Git-Author: Maciej W. Rozycki X-Git-Refname: refs/heads/master X-Git-Oldrev: 1dd024239b551e55a867880d898a63fcf479b717 X-Git-Newrev: c4de64f8f6df99078d55d329bed24bbe3b963aba Message-Id: <20220701161240.34C9F385E013@sourceware.org> Date: Fri, 1 Jul 2022 16:12:40 +0000 (GMT) X-BeenThere: gdb-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2022 16:12:40 -0000 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dc4de64f8f6df= 99078d55d329bed24bbe3b963aba commit c4de64f8f6df99078d55d329bed24bbe3b963aba Author: Maciej W. Rozycki Date: Fri Jul 1 17:11:09 2022 +0100 GDB/doc: Remove extraneous spaces from completion examples =20 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. =20 However in the manual we have completion examples given using a space that actually prevents the example from working. E.g.: =20 (gdb) info bre =20 (nothing) and: =20 (gdb) info bre Display all 200 possibilities? (y or n) =20 as it now goes on to propose the entire symbol table, while: =20 (gdb) info bre (gdb) info breakpoints =20 does the right thing, but is not what is shown in the manual. =20 In other cases an extraneous space is used that does not correspond to the actual completion pattern shown, which gives an impression of sloppiness. =20 Remove extraneous spaces then from completion examples as appropriate. Diff: --- gdb/doc/gdb.texinfo | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f7b02c262b8..ad5bc7db01e 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 =20 @noindent @@ -1945,7 +1945,7 @@ function names in your program that begin with those = characters, for example: =20 @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, typ= e a single quote when you press @key{TAB} or @kbd{M-?} to request word completion: =20 @smallexample -(@value{GDBP}) p 'func< @kbd{M-?} +(@value{GDBP}) p 'func<@kbd{M-?} func() func() (@value{GDBP}) p 'func< @end smallexample @@ -2050,7 +2050,7 @@ usually need to type a quote before the function name= , because function: =20 @smallexample -(@value{GDBP}) b func< @kbd{M-?} +(@value{GDBP}) b func<@kbd{M-?} func() func() (@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)}. =20 @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