Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: gdb-patches@sources.redhat.com
Cc: jari.aalto@cante.net
Subject: [PATCH] gdb: gdb.1 - order options alphabetically in manual page
Date: Wed, 09 Sep 2009 18:20:00 -0000	[thread overview]
Message-ID: <87hbvct24x.fsf@jondo.cante.net> (raw)


Motivation:

    Order of the options would follow the convention used in other GNU
    programs lik Cf. cp(1), mv(1), etc.

Forwarded from:

    http://sourceware.org/bugzilla/show_bug.cgi?id=10505

I have assigned papers to FSF (Emacs). Please let me know if more is
needed.

Jari

[ChangeLog]

2009-09-09  Jari Aalto  <jari.aalto@cante.net>

	* gdb.1: Order options alphabetically.

[PATCH]

From 539edd1a9af966d16f3391edece93702a86c7155 Mon Sep 17 00:00:00 2001
From: Jari Aalto <jari.aalto@cante.net>
Date: Sat, 8 Aug 2009 10:18:20 +0300
Subject: [PATCH] gdb.1: Order options alphabetically

Signed-off-by: Jari Aalto <jari.aalto@cante.net>
---
 gdb/gdb.1 |  148 +++++++++++++++++++++++++------------------------------------
 1 files changed, 60 insertions(+), 88 deletions(-)

diff --git a/gdb/gdb.1 b/gdb/gdb.1
index 809578f..18550b4 100644
--- a/gdb/gdb.1
+++ b/gdb/gdb.1
@@ -205,90 +205,11 @@ in sequential order.  The order makes a difference when the
 `\|\c
 .B \-x\c
 \&\|' option is used.
-
-.TP
-.B \-help
-.TP
-.B \-h
-List all options, with brief explanations.
-
-.TP
-.BI "\-symbols=" "file"\c
-.TP
-.BI "\-s " "file"\c
-\&
-Read symbol table from file \c
-.I file\c
-\&.
-
-.TP
-.B \-write
-Enable writing into executable and core files.
-
-.TP
-.BI "\-exec=" "file"\c
-.TP
-.BI "\-e " "file"\c
-\&
-Use file \c
-.I file\c
-\& as the executable file to execute when
-appropriate, and for examining pure data in conjunction with a core
-dump.
-
-.TP
-.BI "\-se=" "file"\c
-\&
-Read symbol table from file \c
-.I file\c
-\& and use it as the executable
-file.
-
-.TP
-.BI "\-core=" "file"\c
-.TP
-.BI "\-c " "file"\c
-\&
-Use file \c
-.I file\c
-\& as a core dump to examine.
-
-.TP
-.BI "\-command=" "file"\c
-.TP
-.BI "\-x " "file"\c
-\&
-Execute GDB commands from file \c
-.I file\c
-\&.  
-
-.TP
-.BI "\-directory=" "directory"\c
 .TP
-.BI "\-d " "directory"\c
+.BI "\-b " "bps"\c
 \&
-Add \c
-.I directory\c
-\& to the path to search for source files.
-.PP
-
-.TP
-.B \-nx
-.TP
-.B \-n
-Do not execute commands from any `\|\c
-.B .gdbinit\c
-\&\|' initialization files.
-Normally, the commands in these files are executed after all the
-command options and arguments have been processed.
-
-
-.TP
-.B \-quiet
-.TP
-.B \-q
-``Quiet''.  Do not print the introductory and copyright messages.  These
-messages are also suppressed in batch mode.
+Set the line speed (baud rate or bits per second) of any serial
+interface used by GDB for remote debugging.
 
 .TP
 .B \-batch
@@ -316,6 +237,12 @@ Program\ exited\ normally.
 terminates) is not issued when running in batch mode.
 
 .TP
+.B \-c FILE, \-core=FILE
+Use file \c
+.I file\c
+\& as a core dump to examine.
+
+.TP
 .BI "\-cd=" "directory"\c
 \&
 Run GDB using \c
@@ -324,9 +251,21 @@ Run GDB using \c
 instead of the current directory.
 
 .TP
-.B \-fullname
+.B \-d DIRECTORY, \-directory=DIRECTORY
+Add \c
+.I directory\c
+\& to the path to search for source files.
+
+.TP
+.B \-e FILE, -exec=FILE
+Use file \c
+.I file\c
+\& as the executable file to execute when
+appropriate, and for examining pure data in conjunction with a core
+dump.
+
 .TP
-.B \-f
+.B \-f, \-fullname
 Emacs sets this option when it runs GDB as a subprocess.  It tells GDB
 to output the full file name and line number in a standard,
 recognizable fashion each time a stack frame is displayed (which
@@ -341,10 +280,34 @@ Emacs-to-GDB interface program uses the two `\|\c
 a signal to display the source code for the frame.
 
 .TP
-.BI "\-b " "bps"\c
-\&
-Set the line speed (baud rate or bits per second) of any serial
-interface used by GDB for remote debugging.
+.B \-h, \-help
+List all options, with brief explanations.
+
+.TP
+.B \-n, \-nx
+Do not execute commands from any `\|\c
+.B .gdbinit\c
+\&\|' initialization files.
+Normally, the commands in these files are executed after all the
+command options and arguments have been processed.
+
+.TP
+.B -s FILE, \-symbols=FILE
+Read symbol table from file \c
+.I file\c
+\&.
+
+.TP
+.BI "\-se=" "file"\c
+Read symbol table from file \c
+.I file\c
+\& and use it as the executable
+file.
+
+.TP
+.B \q, \-quiet
+``Quiet''.  Do not print the introductory and copyright messages.  These
+messages are also suppressed in batch mode.
 
 .TP
 .BI "\-tty=" "device"\c
@@ -354,6 +317,15 @@ Run using \c
 \& for your program's standard input and output.
 .PP
 
+.TP
+.B \-write
+Enable writing into executable and core files.
+
+.TP
+.B \-x FILE, \-command=FILE
+Execute GDB commands from file \c
+.I file\c
+\&.
 .SH "SEE ALSO"
 .RB "`\|" gdb "\|'"
 entry in
-- 
1.6.3.3



             reply	other threads:[~2009-09-09 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 18:20 Jari Aalto [this message]
2009-09-10  1:08 ` Joel Brobecker
2009-09-10  1:32   ` Daniel Jacobowitz
2009-09-10 22:52     ` Joel Brobecker
2009-09-11  8:10       ` Eli Zaretskii
2009-09-11 23:17         ` Joel Brobecker
2009-09-12  8:31           ` Eli Zaretskii
2009-09-12 18:35             ` Joel Brobecker
2009-10-11 21:22               ` Daniel Jacobowitz
2009-10-11 23:25                 ` Joel Brobecker
2009-09-16 15:49 ` Joel Brobecker
2009-09-16 17:23   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hbvct24x.fsf@jondo.cante.net \
    --to=jari.aalto@cante.net \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox