Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org, gdb@sources.redhat.com
Subject: Re: Special characters in doc strings of GDB commands
Date: Sun, 11 Feb 2007 20:43:00 -0000	[thread overview]
Message-ID: <uk5yo5u0a.fsf@gnu.org> (raw)
In-Reply-To: <20070211180855.GA24482@nevyn.them.org> (message from Daniel 	Jacobowitz on Sun, 11 Feb 2007 13:08:55 -0500)

> Date: Sun, 11 Feb 2007 13:08:55 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> I haven't thought about it.  Probably we'd have to add an additional
> argument to everywhere that registers a command, to provide the string
> explicitly.  I'm not thrilled with the idea of duplicating that much
> text though!

Right.  Another possibility would be to enclose the short description
part in some control sequence, which will be stripped by the commands
that print the doc strings.  For example, like makeinfo uses ^[..^]
for similar purposes.


WARNING: multiple messages have this Message-ID

From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org, gdb@sources.redhat.com
Subject: Re: Special characters in doc strings of GDB commands
Date: Mon, 12 Feb 2007 03:11:00 -0000	[thread overview]
Message-ID: <uk5yo5u0a.fsf@gnu.org> (raw)
Message-ID: <20070212031100.VI5hocjRpyIJGUQ6GzlhRAIKVjhgTxCKUfkTGuwrbmw@z> (raw)
In-Reply-To: <20070211180855.GA24482@nevyn.them.org> (message from Daniel 	Jacobowitz on Sun, 11 Feb 2007 13:08:55 -0500)

> Date: Sun, 11 Feb 2007 13:08:55 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> I haven't thought about it.  Probably we'd have to add an additional
> argument to everywhere that registers a command, to provide the string
> explicitly.  I'm not thrilled with the idea of duplicating that much
> text though!

Right.  Another possibility would be to enclose the short description
part in some control sequence, which will be stripped by the commands
that print the doc strings.  For example, like makeinfo uses ^[..^]
for similar purposes.


  parent reply	other threads:[~2007-02-11 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 11:37 Eli Zaretskii
2007-02-10 20:47 ` Daniel Jacobowitz
2007-02-11  4:13   ` Eli Zaretskii
2007-02-11 18:09     ` Daniel Jacobowitz
2007-02-11 20:17       ` Daniel Jacobowitz
2007-02-11 20:43       ` Eli Zaretskii [this message]
2007-02-12  3:11         ` Eli Zaretskii
2007-02-12 17:25         ` Daniel Jacobowitz
2007-02-12 17:58   ` Jim Blandy

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=uk5yo5u0a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=gdb@sourceware.org \
    /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