From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jsmith@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: "commands" command in user defined command
Date: Tue, 14 Aug 2001 00:07:00 -0000 [thread overview]
Message-ID: <6480-Tue14Aug2001100644+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B789BF5.90247675@redhat.com>
> Date: Mon, 13 Aug 2001 22:33:09 -0500
> From: Jackie Smith Cashion <jsmith@redhat.com>
>
> I feel that a better solution is to create a "sister" function
> user_commands_command. This function is almost a copy of
> commands_command except that instead of reading the command list
> interactively, it receives a pointer to the command list in an argument.
I don't have an opinion on this proposal, but if it gets approved,
please remember to update the user manual accordingly.
prev parent reply other threads:[~2001-08-14 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 20:35 Jackie Smith Cashion
2001-08-14 0:07 ` Eli Zaretskii [this message]
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=6480-Tue14Aug2001100644+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jsmith@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