Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Allow GDB to _not_ load a previous command history
Date: Sat, 25 Jan 2020 11:22:00 -0000	[thread overview]
Message-ID: <83d0b8q935.fsf@gnu.org> (raw)
In-Reply-To: <20200124212900.30367-1-andrew.burgess@embecosm.com> (message	from Andrew Burgess on Fri, 24 Jan 2020 21:29:00 +0000)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Fri, 24 Jan 2020 21:29:00 +0000
> 
> I've updated the manual, and added some tests.
> 
> gdb/ChangeLog:
> 
> 	* top.c (write_history_p): Add comment.
> 	(show_write_history_p): Add header comment, give a different
> 	message when history writing is on, but the history filename is
> 	empty.
> 	(history_filename): Add comment.
> 	(history_filename_empty): New function.
> 	(show_history_filename): Add header comment, give a different
> 	message when the filename is empty.
> 	(init_history): Compare history_filename against nullptr, and only
> 	read history if the filename is not empty.
> 	(set_history_filename): Add header comment, and only make
> 	non-empty filenames absolute.
> 	(init_main): Make the filename argument to 'set history filename'
> 	optional.
> 
> gdb/doc/ChangeLog:
> 
> 	* gdb.texinfo (Command History): Extend description for
> 	GDBHISTFILE and GDBHISTSIZE, add detail about the filename for
> 	'set history filename' being optional.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/default.exp: Remove test of 'set history filename'.
> 	* gdb.base/gdbinit-history.exp: Add tests for setting the history
> 	filename to the empty string.
> 	* lib/gdb.exp (gdb_init): Unset environment variables GDBHISTFILE
> 	and GDBHISTSIZE.

Thanks.  This should also be announced in NEWS.

>  @cindex save command history
>  @kindex set history save
>  @item set history save
>  @itemx set history save on
>  Record command history in a file, whose name may be specified with the
> -@code{set history filename} command.  By default, this option is disabled.
> +@code{set history filename} command.  By default, this option is
> +disabled.  The command history will be recorded when @value{GDBN}
> +exits.
>  
>  @item set history save off
> -Stop recording command history in a file.
> +Don't record the command history into the file specified by @code{set
> +history filename} when @value{GDBN} exits.

This should say that if the history file name is an empty string, that
disables saving the history, even if saving it is set on.


  reply	other threads:[~2020-01-25  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 22:54 Andrew Burgess
2020-01-25 11:22 ` Eli Zaretskii [this message]
2020-02-27 12:32   ` [PATCHv2] " Andrew Burgess
2020-02-28  7:48     ` Eli Zaretskii
2020-03-02 19:21       ` 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=83d0b8q935.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --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