Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sorin Otescu <sorinu@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for hooking prefix commands
Date: Wed, 09 Mar 2011 14:15:00 -0000	[thread overview]
Message-ID: <83hbbcpf4q.fsf@gnu.org> (raw)
In-Reply-To: <4D7786A1.8020806@gmail.com>

> Date: Wed, 09 Mar 2011 15:54:41 +0200
> From: Sorin Otescu <sorinu@gmail.com>
> 
> I see some problems with that approach, even if it works. What happens 
> if two or more commands
> have the same second word ?  Which one would be used ?

I see no problem.  For hooking "target remote" you'd say

  define target hook-remote

and for hooking "foo remote" you'd say

  define foo hook-remote

This is what the manual says.


  reply	other threads:[~2011-03-09 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 12:35 Sorin Otescu
2011-03-09 12:58 ` Eli Zaretskii
2011-03-09 13:36   ` Sorin Otescu
2011-03-09 14:01     ` Eli Zaretskii
2011-03-09 14:03       ` Sorin Otescu
2011-03-09 14:15         ` Eli Zaretskii [this message]
2011-03-09 14:22         ` Eli Zaretskii
2011-03-09 15:08           ` Sorin Otescu

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=83hbbcpf4q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sorinu@gmail.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