Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv3 12/11] New options {relative,basename}-with-system-absolute
Date: Wed, 30 Jan 2013 17:15:00 -0000	[thread overview]
Message-ID: <8338xiiodg.fsf@gnu.org> (raw)
In-Reply-To: <20130130074820.GA15998@host2.jankratochvil.net>

> Date: Wed, 30 Jan 2013 08:48:20 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -115,7 +115,8 @@ show print type typedefs
>    Control whether typedef definitions are displayed by "ptype".
>    The default is to show them.
>  
> -set filename-display basename|relative|absolute
> +set filename-display basename|relative|absolute|relative-with-system-absolute
> +                     |basename-with-system-absolute

Can't say I like these too-old names.

Otherwise, OK for this part.

> +@item set filename-display relative-with-system-absolute
> +Determine whether a source filename comes from file having separate debug
> +information file.  In such case display the source filename as absolute one.
> +Otherwise display it relative to the compilation directory.

The option controls how file names are displayed, so starting its
description with "Determine ..." is not the best way.  That first
sentence got me puzzled for a few seconds.

I suggest something like this:

  Display as absolute those source file names that come from files
  with separate debug info, and all the other source file names as
  relative to their compilation directory.

> +@item set filename-display basename-with-system-absolute
> +Determine whether a source filename comes from file having separate debug
> +information file.  In such case display the source filename as absolute one.
> +Otherwise display only basename of the filename.

Similarly here: start with "Display ..." as this what the option
controls.

> +Files having separate debug information file are expected to come from system
> +shared libraries.

This repetition is unnecessary.

OK with these changes.

Thanks.


  reply	other threads:[~2013-01-30 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:10 [patchv2 " Jan Kratochvil
2013-01-30  7:48 ` [patchv3 " Jan Kratochvil
2013-01-30 17:15   ` Eli Zaretskii [this message]
2013-01-30 18:30     ` Eli Zaretskii
2013-01-30 18:53       ` Jan Kratochvil
2013-01-30 20:11         ` Eli Zaretskii
2013-01-30 21:48           ` Doug Evans
2013-01-31  3:49             ` Eli Zaretskii
2013-01-31 18:07               ` Doug Evans
2013-01-31 18:54                 ` Eli Zaretskii
2013-02-01  3:41                   ` Doug Evans
2013-02-01  8:09                     ` Eli Zaretskii
2013-02-02 18:12     ` Jan Kratochvil
2013-02-01 20:59   ` Tom Tromey

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=8338xiiodg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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