Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: fnasser@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb.ini vs. .gdbinit on Cygwin
Date: Fri, 02 Nov 2001 01:33:00 -0000	[thread overview]
Message-ID: <8632-Tue13Nov2001203408+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3BF1612E.94883F9A@redhat.com> (message from Fernando Nasser on Tue, 13 Nov 2001 13:06:38 -0500)

> Date: Tue, 13 Nov 2001 13:06:38 -0500
> From: Fernando Nasser <fnasser@redhat.com>
> 
> > As a resort we could
> > begin to support an environment variable GDBINIT or similar which
> > contains the name/path of the GDB init file.  That would have the
> > advantage to be mostly host independent.
> > 
> 
> That would have to go through a public gdb discussion as it would 
> affect other platforms as well.
> 
> And what we need is to accommodate users with an older setup and 
> give them an incentive to switch.  The warning message (if no
> .gdbinit was fond and a gdb.ini was found instead) accomplishes
> both goals.
> 
> Eli, what do you think of that solution?  

I generally don't like environment variables unless they are
absolutely necessary.  This doesn't seem to be the case.  Other
platforms don't need it.  Users will have to set the variable in
order to get the functionality.

It's simply a back compatibility issue, that's all.  I like your
suggestion, to support both the old and the new names, best.  It
seems to be silently doing the Right Thing, which is what I expect
from good solutions: you shouldn't be aware that there was a problem
to begin with ;-)

But I don't want to make this an issue between myself and the Cygwin
maintainers.  I just made a comment in the hope that it will be
useful; if the Cygwin maintainers have strong feelings about tossing
gdb.ini and never looking back, it's between them and the Cygwin
users.  Just be sure to document the change in the manual.


  reply	other threads:[~2001-11-13 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01  8:47 Corinna Vinschen
2001-11-01  8:59 ` gdb.ini vs. .gdbinit on cygwin Christopher Faylor
2001-11-01  9:08   ` Corinna Vinschen
2001-11-01 11:21 ` gdb.ini vs. .gdbinit on Cygwin Eli Zaretskii
2001-11-01 15:35   ` Fernando Nasser
2001-11-01 15:47     ` Corinna Vinschen
2001-11-01 16:14       ` Eli Zaretskii
2001-11-02  1:14         ` Corinna Vinschen
2001-11-01 16:50       ` Fernando Nasser
2001-11-02  1:33         ` Eli Zaretskii [this message]
2001-11-01 15:55     ` Eli Zaretskii
2001-11-02 10:45       ` gdb.ini vs. .gdbinit on cygwin Christopher Faylor
2001-11-02 11:01         ` Stan Shebs

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=8632-Tue13Nov2001203408+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=fnasser@redhat.com \
    --cc=gdb@sources.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