From: Waqar Hameed <whame91@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] objdump: Round ASCII art lines in jump visualization
Date: Tue, 18 Jul 2023 19:21:20 +0200 [thread overview]
Message-ID: <874jm1ksv1.fsf@gmail.com> (raw)
In-Reply-To: <75e3c5a2-2098-90e6-13b0-4a007adcc58b@redhat.com>
On Tue, Jul 18, 2023 at 16:24 Nick Clifton <nickc@redhat.com> wrote:
>> Lines with rounded corners are easier to follow (and easier on the
>> eyes). Use `,` and `'` instead of `/` and `\`, respectively, when
>> drawing lines for jumps.
>
> Well this is kind of a personal thing, and not everyone may agree with
> your choice of characters. So how about allowing the user to select the
> characters that they like ? For example if you added a new command line
> option:
>
> --visualize-jump-chars="/,+>'"
>
> which could then be used to provide the characters displayed at various
> points on the graph. Obviously this would be a more complicated patch,
> and would require adding some more documentation, but overall I think that
> it would be worthwhile...
I understand that this is highly subjective and not everyone would agree
with the argument stated in the commit message (I guess the "scientific
method" would be to do a survey :) ).
I don't think an option that specifies characters would make much sense;
there is only a small subset of characters that qualifies to represent
lines. An option to choose "ASCII style" is probably better, e.g.
`--visualize-jumps=round` or something.
However, I'm OK with just dropping this patch. It's not really a big
deal.
next prev parent reply other threads:[~2023-07-18 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 21:47 Waqar Hameed
2023-07-18 15:24 ` Nick Clifton
2023-07-18 17:21 ` Waqar Hameed [this message]
2023-07-19 10:18 ` Nick Clifton
2024-04-23 15:11 ` Nick Clifton
2024-04-23 17:09 ` Waqar Hameed
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=874jm1ksv1.fsf@gmail.com \
--to=whame91@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).