From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [patch] Save the history by default
Date: Wed, 09 Sep 2009 16:42:00 -0000 [thread overview]
Message-ID: <837hw82hsc.fsf@gnu.org> (raw)
In-Reply-To: <20090908203645.GA16820@host0.dyn.jankratochvil.net>
> Date: Tue, 8 Sep 2009 22:36:45 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb@sourceware.org, gdb-patches@sourceware.org
>
> > How about trying both, like we do with .gdbinit?
>
> .gdbinit is being only read, multiple such files can be read.
>
> History file should be (also) written to. History file should never be
> readonly.
I didn't mean to use more than a single history file. What I meant
was to look for that file in both places, and use the first one you
find.
> Formerly I had the patch below (this mail is not a submit for approval).
> Modulo some stat() vs. access() it may be what you suggest?
Looks like it, yes.
> Still I find such behavior too complicated to be convenient and
> therefore useful for this case. One will get rather surprised why
> randomly this or that time (s)he has or does not have the history
> available.
How could that happen? If the file will be found with your suggested
code, it will certainly be found with what I suggest. Or am I missing
something?
next prev parent reply other threads:[~2009-09-09 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
2009-09-09 22:32 ` Tom Tromey
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=837hw82hsc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@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