Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] [+doc] New -iex and -ix: -ex and -x before inferior load
Date: Sat, 25 Feb 2012 17:06:00 -0000	[thread overview]
Message-ID: <20120225165342.GA28961@host2.jankratochvil.net> (raw)
In-Reply-To: <834nuesy34.fsf@gnu.org>

On Sat, 25 Feb 2012 16:59:43 +0100, Eli Zaretskii wrote:
> > +--init-command=FILE, -ix          Like --init-command, -x but execute it
> > +                                  before loading inferior.
> > +--init-eval-command=COMMAND, -iex Like --eval-command=COMMAND, -ex but
> > +                                  execute it before loading inferior.
> 
> Is it really a good idea to have 2- or 3-letter short options?  It
> started with -nw and -nx, which might make sense, then we added -ex,
> and now -ix and -iex?  If noting else, this will prevent us from ever
> having -e and -i.
> 
> How about if we don't have short versions of these at all?

Originally I had -initx and -initex, if it would be OK for you.

These options are just for convenience, which contradicts me the long options
--init-eval-command.  Still even --init-eval-command is better than nothing.


> OK with those changes.

I will change those.


Thanks,
Jan


  reply	other threads:[~2012-02-25 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 13:55 Jan Kratochvil
2012-02-25 16:54 ` Eli Zaretskii
2012-02-25 17:06   ` Jan Kratochvil [this message]
2012-02-28 16:34     ` Doug Evans
2012-03-16 20:39       ` ping: " Jan Kratochvil
2012-03-16 20:51         ` Tom Tromey
2012-02-28 16:28   ` Doug Evans
2012-03-19 18:20 ` [commit] " Jan Kratochvil

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=20120225165342.GA28961@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --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