Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*
Date: Fri, 30 Mar 2012 07:26:00 -0000	[thread overview]
Message-ID: <83hax61rey.fsf@gnu.org> (raw)
In-Reply-To: <20120329091258.GD25449@host2.jankratochvil.net>

> Date: Thu, 29 Mar 2012 11:12:58 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> it does not change any default behavior (that's done in [patch 6/6]) but it
> gives an option to warn on .gdbinit files (which become deprecated).

Thanks.

> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -141,7 +141,7 @@ set auto-load python-scripts on|off
>  show auto-load python-scripts
>    Control auto-loading of Python script files.
>  
> -set auto-load local-gdbinit on|off
> +set auto-load local-gdbinit on|off|warn-and-on|warn-and-off
>  show auto-load local-gdbinit
>    Control loading of init file (.gdbinit) from current directory.

OK.

>  If enabled, canned sequences of commands are loaded when debugger starts\n\
>  from .gdbinit file in current directory.  Such files are deprecated,\n\
>  use script associated with inferior executable file instead.\n\
   ^^^^^^^^^^
Either "use a script" or "use scripts", probably the former.

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -1287,13 +1287,16 @@ Processes command line options and operands.
>  @item
>  Reads and executes the commands from init file (if any) in the current
>  working directory as long as @samp{set auto-load local-gdbinit} is set to
> -@samp{yes} (@pxref{Current Directory Init File}).
> +@samp{yes} or @samp{warn-and-yes} (@pxref{Current Directory Init File}).
>  This is only done if the current directory is
>  different from your home directory.  Thus, you can have more than one
>  init file, one generic in your home directory, and another, specific
>  to the program you are debugging, in the directory where you invoke
>  @value{GDBN}.
>  
> +This feature is deprecated, please use @ref{objfile-gdb.rc file} instead;

"objfile" should be in @var, and it should explain what is "objfile".

>  gdb-scripts:  Canned sequences of commands auto-loading is on.
>  libthread-db:  Inferior specific libthread_db auto-loading is on.
> -local-gdbinit:  Current directory .gdbinit script auto-loading is on.
> +local-gdbinit:  Current directory .gdbinit script auto-loading is yes.

Why "yes"?

> +as the @samp{local-gdbinit} feature is deprecated in the favor

"in favor", without "the".

> +of @xref{objfile-gdb.rc file}.

Again, "objfile" should be in @var.

OK with those changes.

> +		warning (_("Reading file .gdbinit in current directory but it "
> +			   "has been deprecated and the reading will be "
> +			   "removed.  %s"),

"reading will be removed" is very ambiguous.  Suggest something like

  Reading of .gdbinit files in current directory has been deprecated
  and will be removed in a future version of GDB.


  parent reply	other threads:[~2012-03-30  7:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  9:13 Jan Kratochvil
2012-03-29 20:58 ` Doug Evans
2012-03-30  6:28   ` Eli Zaretskii
2012-03-30  6:33     ` Doug Evans
2012-03-30  6:45       ` Jan Kratochvil
2012-03-30 18:08     ` suspend: " Jan Kratochvil
2012-03-30  7:26 ` Eli Zaretskii [this message]
2012-04-02 20:31   ` [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*] Jan Kratochvil
2012-04-02 21:10     ` Eli Zaretskii
2012-04-02 21:13       ` Jan Kratochvil
2012-04-02 21:19         ` Eli Zaretskii
2012-04-03 18:33   ` [patch#2 3/6] set auto-load local-gdbinit warn-and-* Jan Kratochvil
2012-04-05 16:15     ` Eli Zaretskii
2012-04-05 21:00       ` Jan Kratochvil
2012-04-05 16:28     ` Doug Evans
2012-04-05 16:53       ` Jan Kratochvil
2012-04-05 17:03         ` Doug Evans

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=83hax61rey.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