From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] gdb: use get_standard_config_dir when looking for .gdbinit
Date: Thu, 08 Oct 2020 09:52:14 +0300 [thread overview]
Message-ID: <83eem98b1d.fsf@gnu.org> (raw)
In-Reply-To: <92f3b4d4a87643bbb9768fbcb9ee8c77cd5ba8de.1601927355.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Wed, 7 Oct 2020 21:05:06 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed, 7 Oct 2020 21:05:06 +0100
> Cc: Tom Tromey <tom@tromey.com>
>
> This commit effectively changes the default location of the .gdbinit
> file, while maintaining backward compatibility.
>
> For non Apple hosts the .gdbinit file will now be looked for in the
> following locations:
>
> $XDG_CONFIG_HOME/gdb/gdbinit
> $HOME/.config/gdb/gdbinit
> $HOME/.gdbinit
>
> On Apple hosts the search order is instead:
>
> $HOME/Library/Preferences/gdb/gdbinit
> $HOME/.gdbinit
Thanks.
I still wonder why we treat Apple specially here.
> +Do not execute commands found in any initialization file
"files"
Also, I think this should say "in any startup or initialization
files", as startup file loading is also prevented, right?
> +(@pxref{Initialization Files}).
There should be a cross-reference to where startup files are described
as well.
> +As the system wide and home directory initialization files are
> +@value{GDBN} will check the current directory for a file called
> +@file{./.gdbinit}. It is loaded last, after command line options
^^^^^^^^^^
The "./" part is redundant here.
next prev parent reply other threads:[~2020-10-08 6:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 20:05 [PATCH 0/7] Adding startup files to GDB Andrew Burgess
2020-10-07 20:05 ` [PATCH 1/7] Add get_standard_config_dir function Andrew Burgess
2020-10-07 20:05 ` [PATCH 2/7] gdb: use get_standard_config_dir when looking for .gdbinit Andrew Burgess
2020-10-08 6:52 ` Eli Zaretskii via Gdb-patches [this message]
2020-11-02 10:20 ` Andrew Burgess
2020-10-22 19:07 ` Tom Tromey
2020-11-09 13:52 ` Tom Tromey
2020-11-09 13:55 ` Tom Tromey
2020-10-07 20:05 ` [PATCH 3/7] gdb: new function to wrap up executing command line scripts/commands Andrew Burgess
2020-10-08 15:25 ` Aktemur, Tankut Baris via Gdb-patches
2020-11-02 9:48 ` Andrew Burgess
2020-10-22 19:08 ` Tom Tromey
2020-10-07 20:05 ` [PATCH 4/7] gdb: process startup files and startup command line options Andrew Burgess
2020-10-08 6:28 ` Eli Zaretskii via Gdb-patches
2020-10-07 20:05 ` [PATCH 5/7] gdb: add mechanism to auto-save startup options Andrew Burgess
2020-10-08 6:36 ` Eli Zaretskii via Gdb-patches
2020-10-07 20:05 ` [PATCH 6/7] Let the user control the startup style Andrew Burgess
2020-10-08 6:40 ` Eli Zaretskii via Gdb-patches
2020-10-07 20:05 ` [PATCH 7/7] Add "set startup-quietly" Andrew Burgess
2020-10-08 6:44 ` Eli Zaretskii via Gdb-patches
2020-10-08 6:56 ` [PATCH 0/7] Adding startup files to GDB Eli Zaretskii via Gdb-patches
2020-10-22 19:02 ` Tom Tromey
2020-10-28 15:29 ` Andrew Burgess
2021-01-11 16:45 ` Andrew Burgess
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=83eem98b1d.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=andrew.burgess@embecosm.com \
--cc=eliz@gnu.org \
--cc=tom@tromey.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