public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26996] New: document command in multi-line context doesn't work
Date: Wed, 02 Dec 2020 14:35:48 +0000	[thread overview]
Message-ID: <bug-26996-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26996

            Bug ID: 26996
           Summary: document command in multi-line context doesn't work
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

While it's possible to have a multi-line define inside a define:

(gdb) define define-my-command
Type commands for definition of "define-my-command".
End with a line saying just "end".
>define my-command
 >print 1
 >end
>end

It's not possible to have a multi-line document inside a define in a similar
way:

(gdb) define document-my-command
Type commands for definition of "document-my-command".
End with a line saying just "end".
>document my-command
>end

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-12-02 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 14:35 simark at simark dot ca [this message]
2020-12-02 14:36 ` [Bug gdb/26996] " simark at simark dot ca
2020-12-16  3:11 ` rae.kim at gmail dot com
2021-05-09 23:58 ` brobecker at gnat dot com

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=bug-26996-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).