From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch] -iex and -ix: Execute them _after_ gdbinits
Date: Tue, 19 Jun 2012 07:59:00 -0000 [thread overview]
Message-ID: <CADPb22SXU_Hh9c0k=+pihYADandJ8CJSTuJFf4vV_0rcTgo19g@mail.gmail.com> (raw)
In-Reply-To: <20120616213126.GA12840@host2.jankratochvil.net>
On Sat, Jun 16, 2012 at 2:31 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Sat, 16 Jun 2012 23:14:15 +0200, Eli Zaretskii wrote:
>> My concern is about what happens before ~/.gdbinit is loaded, so
>> nothing that happens after that can resolve that.
>
> I do not understand which command would you want to run before ~/.gdbinit.
> Real world ~/.gdbinit should only change settings or define new commands.
>
>
>> > I have not found a use case where the current behavior is better.
>>
>> It doesn't have to be better. It has the advantage of being there
>> first. It's the new behavior that must have a significant advantage
>> to justify an incompatible change of behavior.
>
> The idea is that this is not a "change" as 7.4 did not have -iex at all.
> -iex/-ix is a new feature for 7.5 so I am trying to make it right before it
> becomes a standard.
I'm not sure I have an opinion on the order of -iex vs ~/.gdbinit (etc.).
I do believe, however, that we need to have the freedom to change
features introduced after the previous release and before the next if
we have reason to believe we got it wrong.
[IOW, the fact that we're changing behaviour here is less important to
deciding what behaviour we want.]
next prev parent reply other threads:[~2012-06-19 7:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 19:54 Jan Kratochvil
2012-06-16 20:05 ` Eli Zaretskii
2012-06-16 20:13 ` Jan Kratochvil
2012-06-16 21:14 ` Eli Zaretskii
2012-06-16 21:32 ` Jan Kratochvil
2012-06-17 2:52 ` Eli Zaretskii
2012-06-17 6:50 ` Jan Kratochvil
2012-06-20 19:01 ` Jan Kratochvil
2012-06-20 19:38 ` Eli Zaretskii
2012-06-22 7:51 ` Jan Kratochvil
2012-06-22 9:44 ` Eli Zaretskii
2012-06-22 11:32 ` Jan Kratochvil
2012-06-22 13:26 ` Eli Zaretskii
2012-06-22 13:48 ` Jan Kratochvil
2012-06-22 14:19 ` Tom Tromey
2012-06-22 14:41 ` Eli Zaretskii
2012-07-02 12:05 ` [commit] " Jan Kratochvil
2012-06-22 14:18 ` Tom Tromey
2012-06-19 7:59 ` Doug Evans [this message]
2012-06-22 14:17 ` Tom Tromey
2012-06-18 16:45 ` Joel Brobecker
2012-06-22 14:17 ` Tom Tromey
2012-06-22 16:12 ` Joel Brobecker
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='CADPb22SXU_Hh9c0k=+pihYADandJ8CJSTuJFf4vV_0rcTgo19g@mail.gmail.com' \
--to=dje@google.com \
--cc=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