From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH,v3 17/17] [gdb/docs] sme: Document SME registers and features
Date: Thu, 27 Apr 2023 12:10:43 +0300 [thread overview]
Message-ID: <83y1mdsnak.fsf@gnu.org> (raw)
In-Reply-To: <11f9bfb1-78cb-80db-fbc6-3262f0f9fdae@arm.com> (message from Luis Machado on Thu, 27 Apr 2023 09:35:15 +0100)
> Date: Thu, 27 Apr 2023 09:35:15 +0100
> Cc: gdb-patches@sourceware.org
> From: Luis Machado <luis.machado@arm.com>
>
> >>> This should use @var, not @code. Also, I'd remove the whitespace
> >>> around "x".
> >>
> >> Fixed. But I used spaces between "x" and the two @var entries because it gets rendered as a single
> >> block of characters like svlxsvl.
> >
> > That doesn't seem possible, since @var produces a different typeface:
> > slanted in the printed version and CAPS in the Info versions. Where
> > did you see svlxsvl?
>
> In the PDF. I mean, it is slanted with the use of @var{}, but not that noticeable.
>
> See the attached pdf. I also attached the info file.
Then maybe use "@var{svl} by @var{svl}"?
> I noticed the info file capitalizes @var{}, which might not be ideal?
That cannot be helped. It isn't ideal, indeed, but given that Info
manuals must be displayed on plain-text terminals, there's not a lot
Texinfo can play with.
next prev parent reply other threads:[~2023-04-27 9:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 4:26 [PATCH 00/17] SME support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-04-11 4:26 ` [PATCH 01/17] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux Luis Machado
2023-04-11 4:26 ` [PATCH 02/17] [gdb/aarch64] refactor: Rename SVE-specific files Luis Machado
2023-04-11 4:26 ` [PATCH 03/17] [gdb/gdbserver] refactor: Simplify SVE interface to read/write registers Luis Machado
2023-04-11 4:26 ` [PATCH 04/17] [gdb/aarch64] sve: Fix return command when using V registers in a SVE-enabled target Luis Machado
2023-04-11 4:26 ` [PATCH 05/17] [gdb/aarch64] sme: Enable SME registers and pseudo-registers Luis Machado
2023-04-11 4:26 ` [PATCH 06/17] [gdbserver/aarch64] refactor: Adjust expedited registers dynamically Luis Machado
2023-04-11 4:26 ` [PATCH 07/17] [gdbserver/aarch64] sme: Add support for SME Luis Machado
2023-04-11 4:26 ` [PATCH 08/17] [gdb/aarch64] sve: Fix signal frame z/v register restore Luis Machado
2023-04-11 4:26 ` [PATCH 09/17] [gdb/aarch64] sme: Signal frame support Luis Machado
2023-04-11 4:26 ` [PATCH 10/17] [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes Luis Machado
2023-04-11 4:26 ` [PATCH 11/17] [gdb/aarch64] sme: Support TPIDR2 signal frame context Luis Machado
2023-04-11 4:26 ` [PATCH 12/17] [binutils/aarch64] sme: Core file support Luis Machado
2023-04-11 4:26 ` [PATCH 13/17] [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping register state to core files Luis Machado
2023-04-11 4:26 ` [PATCH 14/17] [gdb/generic] corefile/bug: Fixup (gcore) core file target description reading order Luis Machado
2023-04-11 4:26 ` [PATCH 15/17] [gdb/aarch64] sme: Core file support for Linux Luis Machado
2023-04-11 4:26 ` [PATCH 16/17] [gdb/testsuite] sme: Add SVE/SME testcases Luis Machado
2023-04-11 4:26 ` [PATCH 17/17] [gdb/docs] sme: Document SME registers and features Luis Machado
2023-04-11 7:09 ` Eli Zaretskii
2023-04-11 7:22 ` Luis Machado
2023-04-12 12:04 ` [PATCH,v2 " Luis Machado
2023-04-13 7:57 ` Eli Zaretskii
2023-04-13 12:17 ` Luis Machado
[not found] ` <83leiv4xsc.fsf@gnu.org>
2023-04-13 16:34 ` Luis Machado
2023-04-13 17:45 ` Eli Zaretskii
2023-04-17 17:19 ` [PATCH,v3 " Luis Machado
2023-04-22 9:21 ` Eli Zaretskii
2023-04-26 15:00 ` Luis Machado
2023-04-26 16:11 ` Eli Zaretskii
2023-04-27 8:35 ` Luis Machado
2023-04-27 9:10 ` Eli Zaretskii [this message]
2023-04-27 9:12 ` Luis Machado
2023-04-11 15:50 ` [PATCH 00/17] SME support for AArch64 gdb/gdbserver on Linux John Baldwin
2023-04-12 8:47 ` Willgerodt, Felix
2023-04-12 9:12 ` Luis Machado
2023-05-19 10:24 [PATCH v2 " Luis Machado
2023-05-19 10:25 ` [PATCH v3 17/17] [gdb/docs] sme: Document SME registers and features Luis Machado
2023-05-19 11:20 ` Eli Zaretskii
2023-06-30 12:10 ` Luis Machado
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=83y1mdsnak.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).