Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, gdb@sourceware.org,
	gdb-patches@sourceware.org
Subject: Re: [patch] Save the history by default
Date: Wed, 09 Sep 2009 19:55:00 -0000	[thread overview]
Message-ID: <200909091954.n89JsvJM001528@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <m3ws47q53t.fsf@fleche.redhat.com> (message from Tom Tromey on 	Wed, 09 Sep 2009 13:40:22 -0600)

> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 09 Sep 2009 13:40:22 -0600
> 
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> 2009-09-08  Jan Kratochvil  <jan.kratochvil@redhat.com>
> Jan> 	Save the command history by default and use a file in $HOME.
> 
> This idea is fine by me.
> 
> I wouldn't mind changing other defaults too.
> We've discussed changing "set print object" a couple of times...
> 
> I did not research this, but please make sure that this patch doesn't
> result in gdb saving history:
> 
> 1. When in MI mode
> 2. When running the test suite
> 
> Other than those possibilities, this seems fine.
> 
> I think for changes to defaults it makes sense to wait a little while to
> let other maintainers speak up in case they have an objection.  So
> please wait a little while before going ahead.

I have no objection to change *this* default since it doesn't really
change how you interact with GDB.  But I'm far less enthousiastic
about changing things like "set print object" that affect the output
GDB generates for commands.


  reply	other threads:[~2009-09-09 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090908200537.GA14676__29508.7702492767$1252440377$gmane$org@host0.dyn.jankratochvil.net>
2009-09-09 19:40 ` Tom Tromey
2009-09-09 19:55   ` Mark Kettenis [this message]
2009-09-09 22:32     ` Tom Tromey
2009-09-08 20:05 Jan Kratochvil
2009-09-08 20:20 ` Eli Zaretskii
2009-09-08 20:37   ` Jan Kratochvil
2009-09-09 16:42     ` Eli Zaretskii

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=200909091954.n89JsvJM001528@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@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