document gdb.init check only performed in home directory

The documentation is a little ambiguous and might be suggesting that
GDB checks all locations where a gdbinit might be located for gdb.ini
files.  This clarifies the current situation.

gdb/doc/ChangeLog:

        * gdb.texinfo (Startup): Minor rewording, and clarify scope of
        gdb.ini warning for Windows port.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index fd776bf..7e83709 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2012-11-08  Joel Brobecker  <brobecker@adacore.com>
+
+       * gdb.texinfo (Startup): Minor rewording, and clarify scope of
+       gdb.ini warning for Windows port.
+
 2012-11-08  Yao Qi  <yao@codesourcery.com>
 
        * gdb.texinfo (Search): Add kindex for 'fo'.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c7777e6..7382352 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -1366,9 +1366,9 @@ can use @kbd{gdb --help}.
 The @value{GDBN} init files are normally called @file{.gdbinit}.
 The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
 the limitations of file names imposed by DOS filesystems.  The Windows
-ports of @value{GDBN} use the standard name, but if they find a
-@file{gdb.ini} file, they warn you about that and suggest to rename
-the file to the standard name.
+port of @value{GDBN} uses the standard name, but if it finds a
+@file{gdb.ini} file in your home directory, it warns you about that
+and suggests to rename the file to the standard name.
 
 
 @node Quitting GDB