From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] Document 'set|show exec-file-mismatch (reload|warn|off)'
Date: Sun, 22 Dec 2019 18:20:00 -0000 [thread overview]
Message-ID: <83tv5sxlx6.fsf@gnu.org> (raw)
In-Reply-To: <afc52b36af331190a8134123b9f1f4110f641dd2.camel@skynet.be> (message from Philippe Waroquiers on Sat, 21 Dec 2019 21:15:48 +0100)
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: gdb-patches@sourceware.org
> Date: Sat, 21 Dec 2019 21:15:48 +0100
>
> However, your comments make me think that the words used
> in the command itself might have to be improved, as the
> word "reload" seems confusing.
Yes, I've misunderstood what it means. The text needs to be rewritten
to make clear what this feature tries to detect. An example you've
shown could be a good idea.
> So, maybe "reload" in 'set exec-file-mismatch reload|warn|off' should be replaced
> by a less confusing word?
>
> Maybe 'set exec-file-mismatch ask-to-load|warn|off' ?
How about ask|warn|off ?
next prev parent reply other threads:[~2019-12-22 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 14:36 [RFA 1/3] New option 'set exec-file-mismatch (reload|warn|off)'. Fixes PR gdb/17626 Philippe Waroquiers
2019-12-21 14:36 ` [RFA 3/3] Document 'set|show exec-file-mismatch (reload|warn|off)' Philippe Waroquiers
2019-12-21 17:44 ` Eli Zaretskii
2019-12-21 20:16 ` Philippe Waroquiers
2019-12-22 18:20 ` Eli Zaretskii [this message]
2019-12-22 2:46 ` Christian Biesinger via gdb-patches
2019-12-22 9:09 ` Philippe Waroquiers
2020-01-08 0:52 ` Tom Tromey
2019-12-21 14:36 ` [RFA 2/3] Test 'set exec-file-mismatch reload|warn|off' Philippe Waroquiers
2019-12-21 14:36 ` [RFA 1/3] Implement 'set/show exec-file-mismatch' Philippe Waroquiers
2020-01-08 0:58 ` 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=83tv5sxlx6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).