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: Fri, 22 Jun 2012 09:44:00 -0000 [thread overview]
Message-ID: <838vffd6l3.fsf@gnu.org> (raw)
In-Reply-To: <20120622075113.GA9742@host2.jankratochvil.net>
> Date: Fri, 22 Jun 2012 09:51:13 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> > Specifically, why isn't it a
> > good feature to be able to execute commands before loading .gdbinit?
>
> I do not see how it could be useful, in such cases one can execute the
> commands after loading /etc/gdbinit or ~/.gdbinit with the same effect.
A simple scenario where this could be useful is when either of these
two files does something conditioned on some variable's value. Then
setting that variable before these are loaded can control what loading
them does.
next prev parent reply other threads:[~2012-06-22 9:44 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 [this message]
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=838vffd6l3.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