From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] -iex and -ix: Execute them _after_ gdbinits
Date: Sun, 17 Jun 2012 02:52:00 -0000 [thread overview]
Message-ID: <83r4teejkj.fsf@gnu.org> (raw)
In-Reply-To: <20120616213126.GA12840@host2.jankratochvil.net>
> Date: Sat, 16 Jun 2012 23:31:49 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> 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.
GDB has a gazillion settings, so this still includes a lot of
possibilities.
> > > 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.
That doesn't matter much nowadays, as people use development snapshots
all the time.
next prev parent reply other threads:[~2012-06-17 2:52 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 [this message]
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
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=83r4teejkj.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