From: Patrick Palka <patrick@parcs.ath.cx>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Patrick Palka <patrick@parcs.ath.cx>
Subject: Re: [PATCH 1/2] Read $GDBHISTSIZE instead of $HISTSIZE
Date: Wed, 17 Jun 2015 18:19:00 -0000 [thread overview]
Message-ID: <CA+C-WL9Qh8i7kFegEpip-rRYv4eb=xA=g3Kqj55v+Su+oKUiWA@mail.gmail.com> (raw)
In-Reply-To: <1432293831-23599-1-git-send-email-patrick@parcs.ath.cx>
On Fri, May 22, 2015 at 7:23 AM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> The HISTSIZE environment variable is generally expected to be read by
> shells, not by applications. Some distros for example globally export
> HISTSIZE in /etc/profile -- with the intention that it only affects
> shells -- and by doing so it renders useless GDB's own mechanism for
> setting the history size via .gdbinit. Also, annoyances may arise when
> HISTSIZE is not interpreted the same way by the shell and by GDB, e.g.
> PR gdb/16999. That can always be fixed on a shell-by-shell basis but it
> may be impossible to be consistent with the behavior of all shells at
> once. Finally it just makes sense to not confound shell environment
> variables with application environment variables.
>
> gdb/ChangeLog:
>
> * NEWS: Add entry.
> * top.c (init_history): Read from GDBHISTSIZE instead of
> HISTSIZE.
> (init_main): Refer to GDBHISTSIZE instead of HISTSIZE.
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Command History): Replace occurrences of HISTSIZE
> with GDBHISTSIZE.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.base/gdbinit-history.exp: Replace occurrences of HISTSIZE
> with GDBHISTSIZE.
> * gdb.base/readline.exp: Likewis.
Committed this change (without the part that explains in the manual
why we don't use HISTSIZE). Eli, what do you think about the
following addendum to the manual?
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 9889b69..c1b11f4 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22644,6 +22644,15 @@ to 256 if this variable is not set.
Non-numeric values of @env{GDBHISTSIZE}
are ignored. If @var{size} is @code{unlimited} or if @env{GDBHISTSIZE} is a
negative number, the number of commands @value{GDBN} keeps in the history list
is unlimited.
+
+Note: In @value{GDBN} version 7.8 and earlier, the @env{HISTSIZE} environment
+variable was read instead of the @env{GDBHISTSIZE} environment variable.
+However, reading @env{HISTSIZE} was problematic since this environment variable
+is usually set with the intention to be read only by the user's shell, and
+differences in interpretation of this environment variable may exist between
+@value{GDBN} and the prevailing shell. So since @value{GDBN} version 7.9 the
+dedicated @env{GDBHISTSIZE} environment variable is instead read for the same
+purpose.
@end table
History expansion assigns special meaning to the character @kbd{!}.
prev parent reply other threads:[~2015-06-17 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 11:24 Patrick Palka
2015-05-22 11:24 ` [PATCH 2/2] Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999] Patrick Palka
2015-05-22 11:57 ` Patrick Palka
2015-05-29 9:32 ` Pedro Alves
2015-06-17 19:18 ` Patrick Palka
2015-06-23 12:56 ` Yao Qi
2015-06-23 14:28 ` Patrick Palka
2015-05-22 12:30 ` [PATCH 1/2] Read $GDBHISTSIZE instead of $HISTSIZE Eli Zaretskii
2015-06-04 15:30 ` Patrick Palka
2015-06-15 14:54 ` Pedro Alves
2015-05-29 11:05 ` Pedro Alves
2015-06-17 18:19 ` Patrick Palka [this message]
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='CA+C-WL9Qh8i7kFegEpip-rRYv4eb=xA=g3Kqj55v+Su+oKUiWA@mail.gmail.com' \
--to=patrick@parcs.ath.cx \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).