From: Tom Tromey <tom@tromey.com>
To: binutils@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 4/4] Redefine FUNCTION in doc.str
Date: Fri, 17 Feb 2023 12:29:05 -0700 [thread overview]
Message-ID: <20230217192905.3160819-5-tom@tromey.com> (raw)
In-Reply-To: <20230217192905.3160819-1-tom@tromey.com>
FUNCTION is identical to func, so simplify doc.str.
2023-02-17 Tom Tromey <tom@tromey.com>
* doc/doc.str (FUNCTION): Call func.
---
bfd/ChangeLog | 4 ++++
bfd/doc/doc.str | 10 +---------
2 files changed, 5 insertions(+), 9 deletions(-)
diff --git a/bfd/doc/doc.str b/bfd/doc/doc.str
index 5077ada9812..f59ff2edd6e 100644
--- a/bfd/doc/doc.str
+++ b/bfd/doc/doc.str
@@ -74,15 +74,7 @@ variable synopsis_seen
;
: FUNCTION
- "@findex " - a
- skip_past_newline
- copy_past_newline
- dup - a x x
- "@subsubsection @code{" - a x x b
- swap
- remchar
- "}\n" - a x b x c
- catstr catstr catstr catstr catstr
+ func
;
: bodytext
--
2.39.1
next prev parent reply other threads:[~2023-02-17 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 19:29 [PATCH 0/4] More fixes to chew documentation Tom Tromey
2023-02-17 19:29 ` [PATCH 1/4] Fix formatting of long function description in chew output Tom Tromey
2023-02-17 19:29 ` [PATCH 2/4] Don't use chew comments for static functions Tom Tromey
2023-02-17 19:29 ` [PATCH 3/4] Hoist the SECTION comment in opncls.c Tom Tromey
2023-02-17 19:29 ` Tom Tromey [this message]
2023-02-20 14:59 ` [PATCH 0/4] More fixes to chew documentation Nick Clifton
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=20230217192905.3160819-5-tom@tromey.com \
--to=tom@tromey.com \
--cc=binutils@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).