Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Allow to document user-defined aliases.
Date: Tue, 26 Jul 2022 14:00:50 +0300	[thread overview]
Message-ID: <83a68wdtp9.fsf@gnu.org> (raw)
In-Reply-To: <459ea883bef4b9af65194bd3e5ed4de78b600c62.camel@skynet.be> (message from Philippe Waroquiers on Mon, 25 Jul 2022 22:35:45 +0200)

> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 25 Jul 2022 22:35:45 +0200
> 
> > But it doesn't do much harm, either.  Moreover, it is useful to tell
> > the user that some handy aliases exist related to the command.
> The idea/reasoning is that if the user documents specifically the alias,
> it means that the alias is not properly documented by the doc of the
> aliased command.

I'm questioning the over-reaching validity of this assumption.  I
understand that this would be your logic, but I'm asking whether some
other GDB users could have a different perspective on this.

> I can for sure implement the alias -s option if there is an agreement
> that this is better.

Let's see what others think.  Mine is just one opinion.

Thanks.

  reply	other threads:[~2022-07-26 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  4:11 Philippe Waroquiers via Gdb-patches
2022-07-25 11:24 ` Eli Zaretskii via Gdb-patches
2022-07-25 20:35   ` Philippe Waroquiers via Gdb-patches
2022-07-26 11:00     ` Eli Zaretskii via Gdb-patches [this message]
2022-08-04 19:12 ` Tom Tromey
2022-08-07 19:14   ` Philippe Waroquiers via Gdb-patches
2022-08-04 19:13 ` 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=83a68wdtp9.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=philippe.waroquiers@skynet.be \
    /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