I see two places that contradict your explanation so I'm a bit confused.

@help plugin plugin
(plugin plugin <command>) -- Returns the plugin(s) that <command> is in.

@plugin help plugin
This plugin exists to help users manage their plugins. Use 'plugin
list' to list the loaded plugins; use 'plugin help' to get this sort
of help from other plugins; use the 'plugin' command itself to
determine what plugin a command exists in.

While the apropos command does something similar and provides the
information I am looking for it also gives additional information.

Grant


On Thu, Jul 24, 2008 at 5:36 AM, Debian Bug Tracking System
<[EMAIL PROTECTED]> wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the supybot package:
>
> #492165: supybot: Plugin plugin command bug
>
> It has been closed by James Vega <[EMAIL PROTECTED]>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact James Vega <[EMAIL 
> PROTECTED]> by
> replying to this email.
>
>
> --
> 492165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492165
> Debian Bug Tracking System
> Contact [EMAIL PROTECTED] with problems
>
>
> ---------- Forwarded message ----------
> From: James Vega <[EMAIL PROTECTED]>
> To: Grant Bowman <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Date: Thu, 24 Jul 2008 08:33:05 -0400
> Subject: Re: Bug#492165: supybot: Plugin plugin command bug
> On Thu, Jul 24, 2008 at 12:23:03AM -0700, Grant Bowman wrote:
>> 1. use supybot-wizard to create a new bot
>> 2. !load Plugin
>> 3. !load Seen
>> 3. !Plugin plugin last
>>
>> Result: The "last" command is available in the Misc plugin.
>>
>> Expected Result: the last command is offered in both the Misc and Seen
>> plugins but is not reported correctly.
>
> Plugin.plugin reports the behavior of calling the given command.  If
> "@somecommand" runs a command instead of reporting that somecommand is
> available in multiple plugins which must be disambiguated, then "@plugin
> somecommand" will only list the plugin providing the somecommand that is
> run.
>
> Misc.apropos will always list all plugins that provide a certain
> command.
>
> In this case, Misc is, by default, registered as the default plugin for
> the last command so it is what Plugin.plugin reports.  If you want
> another plugin's last to be default, take a look at the defaultplugin
> command in the Owner plugin.
>
> --
> James
> GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkiIdoEACgkQDb3UpmEybUC3HACeNCik7TlDJkfES83hZDmxKy5y
> FDUAn3JoR9unYmCFda28gEOwoKT7Ha/I
> =RpwC
> -----END PGP SIGNATURE-----
>
>
> ---------- Forwarded message ----------
> From: Grant Bowman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Thu, 24 Jul 2008 00:23:03 -0700
> Subject: supybot: Plugin plugin command bug
> Package: supybot
> Version: 0.83.3-1
> Severity: normal
>
>
> 1. use supybot-wizard to create a new bot
> 2. !load Plugin
> 3. !load Seen
> 3. !Plugin plugin last
>
> Result: The "last" command is available in the Misc plugin.
>
> Expected Result: the last command is offered in both the Misc and Seen
> plugins but is not reported correctly.
>
> -- System Information:
> Debian Release: lenny/sid
> Architecture: i386 (i686)
>
> Versions of packages supybot depends on:
> ii  python                    2.5.2-0ubuntu1 An interactive high-level
> object-o
> ii  python-support            0.7.5ubuntu1   automated rebuilding
> support for p
>
> supybot recommends no packages.
>
> -- no debconf information
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to