Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, guitton@adacore.com
Subject: Re: Add support for --with-system-gdbinit
Date: Wed, 14 Jan 2009 19:39:00 -0000	[thread overview]
Message-ID: <uiqohwuek.fsf@gnu.org> (raw)
In-Reply-To: <20090114135619.GA24456@caradoc.them.org>

> Date: Wed, 14 Jan 2009 08:56:19 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Jerome Guitton <guitton@adacore.com>, Eli Zaretskii <eliz@gnu.org>
> 
> The path will be automatically relocated if the GDB binary is moved,
> so it can be used for a system-wide directory like /etc or a
> prefixed directory like /opt/vendor/share.

Sorry, I don't understand: what does this mean?  How does one
``relocate a path''?

> Eli, is the doc patch OK?

The doc patch doesn't really say anything useful:

>  @item
>  @cindex init file
> +Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was
> +used when building @value{GDBN}) and executes all the commands in that file.

That's it!  We don't tell what is the name of the file, we don't tell
how to find it, we just tell it _might_ exist and it _might_ be read
by GDB at startup.  That doesn't sound very user-friendly to me.
Contrast that with what the Emacs manual says about site-start.el,
which AFAIU has a similar purpose.

Am I missing something?

At the very least we should have some command-line option (perhaps as
part of "--help") to show where this file should live and what's its
name, and we should describe that right next to the above text.  We
shouldn't assume that the user is the same person who built GDB in the
first place.

Also, doesn't the relocation of the file (whatever it may mean)
warrant some documentation as well?  Assuming I'm a sysadmin who needs
to set up such a site-wide init file, don't I need to know something
else besides what you wrote?


  reply	other threads:[~2009-01-14 19:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 13:56 Daniel Jacobowitz
2009-01-14 19:39 ` Eli Zaretskii [this message]
2009-01-14 19:50   ` Daniel Jacobowitz
2009-01-14 20:22     ` Eli Zaretskii
2009-01-14 20:38       ` Daniel Jacobowitz
2009-01-14 21:55         ` Eli Zaretskii
2009-01-14 23:07           ` Daniel Jacobowitz
2009-01-15  4:10             ` Eli Zaretskii
2009-01-19 14:11     ` Jerome Guitton
2009-01-19 14:20       ` Daniel Jacobowitz
2009-01-19 18:40       ` Eli Zaretskii
2009-01-21 10:54         ` Jerome Guitton
2009-01-21 19:03           ` Eli Zaretskii
2009-01-23 17:24             ` Jerome Guitton
2009-01-23 22:55               ` Eli Zaretskii
2009-01-28 18:00                 ` Jerome Guitton
2009-01-23 17:42           ` Daniel Jacobowitz
2009-01-26  9:12             ` Jerome Guitton
2009-01-26 14:59               ` Daniel Jacobowitz
2009-01-28 15:06                 ` Jerome Guitton
2009-01-16 11:54 ` Jerome Guitton

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=uiqohwuek.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guitton@adacore.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