From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess via Binutils <binutils@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH 1/3] objdump/opcodes: add syntax highlighting to disassembler output
Date: Mon, 28 Feb 2022 08:54:30 -0700 [thread overview]
Message-ID: <877d9fm1ft.fsf@tromey.com> (raw)
In-Reply-To: <a663e46e570fa2deabef1a06ea005c0c70fc0a73.1645043588.git.aburgess@redhat.com> (Andrew Burgess via Binutils's message of "Wed, 16 Feb 2022 20:53:29 +0000")
>>>>> "Andrew" == Andrew Burgess via Binutils <binutils@sourceware.org> writes:
Andrew> I do have an idea about using possibly an environment variable to
Andrew> allow the objdump colors to be customised, but I haven't done anything
Andrew> like that in this commit, the color choices are just fixed in the code
Andrew> for now.
For this, there's some prior art in coreutils and gcc.
There's also GNU libtextstyle, but that may be overkill.
Tom
next prev parent reply other threads:[~2022-02-28 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:53 [PATCH 0/3] disassembler syntax highlighting in objdump (via libopcodes) Andrew Burgess
2022-02-16 20:53 ` [PATCH 1/3] objdump/opcodes: add syntax highlighting to disassembler output Andrew Burgess
2022-02-28 15:54 ` Tom Tromey [this message]
2022-02-16 20:53 ` [PATCH 2/3] opcodes/riscv: implement style support in the disassembler Andrew Burgess
2022-02-19 10:24 ` Andrew Burgess
2022-02-16 20:53 ` [PATCH 3/3] opcodes/i386: partially implement disassembler style support Andrew Burgess
2022-02-17 9:35 ` Jan Beulich
2022-02-17 16:15 ` Andrew Burgess
2022-02-17 16:29 ` Jan Beulich
2022-02-17 22:37 ` Andrew Burgess
2022-02-18 7:14 ` Jan Beulich
2022-02-19 10:54 ` Andrew Burgess
2022-02-21 13:08 ` Jan Beulich
2022-02-21 18:01 ` Andrew Burgess
2022-02-17 3:57 ` [PATCH 0/3] disassembler syntax highlighting in objdump (via libopcodes) Nelson Chu
2022-02-17 16:17 ` Andrew Burgess
2022-03-21 14:33 ` [PATCHv2 " Andrew Burgess
2022-03-21 14:33 ` [PATCHv2 1/3] objdump/opcodes: add syntax highlighting to disassembler output Andrew Burgess
2022-03-21 14:33 ` [PATCHv2 2/3] opcodes/riscv: implement style support in the disassembler Andrew Burgess
2022-03-21 14:33 ` [PATCHv2 3/3] opcodes/i386: partially implement disassembler style support Andrew Burgess
2022-03-24 17:08 ` [PATCHv2 0/3] disassembler syntax highlighting in objdump (via libopcodes) 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=877d9fm1ft.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.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).