Forums Bug Reports mIRC does not process operspy channel list !

Some IRCds have operspy, and bringing up the list of channels with operspy (/list !*), mIRC does not get the list of channels with all the channels, it brings up the list but the list is blank with no channels and no secret channels.

I tried it with XChat and it does work.


/quote help operspy

operspy OPERSPY
operspy
operspy Opers with the "oper_spy" flag will be allowed uses of the following
operspy commands if they are compiled in. Usage will be sent to +Z and all
operspy other servers.
operspy
operspy whois !nick - Gives a full output of channels the user is in.
operspy who !mask - Lists all users networkwide whose nick, ident, host,
operspy server or gecos match the mask.
operspy who !#channel - Gives a full output of users on the channel.
operspy mode !#channel - Gives the full modes of a channel including any keys.
operspy chantrace !#channel - Gives full output despite not being on channel.
operspy masktrace !nick!user@host :gecos - Lists matching users on all servers.
operspy topic !#channel - Gives full output despite not being on channel.
operspy list !#channel - Gives full output despite not being on channel.
operspy list ![options...] - Lists all channels, including secret channels.
operspy End of /HELP.

That's not a bug, by default, /list hides non-text channel, see https://forums.mirc.com/ubbthreads.php/topics/241692/Channels_that_begin_with_do_no#Post241692, you need to uncheck the option (alt + l > hides non-text channels)

Khaled, could we have this turned off by default? It really confuses people more than it helps.

uncheck hide non-text channels did not work sorry to say. /list !* still came up blank.

Ok, then perhaps mIRC could allow a ! there, or just allow anything to be sent to the irc server with /list, which can be done with a simple override of /list in the aliases (alt+D, add "list raw list $1-").

Which version of mIRC are you using? If I remember correctly, someone reported this issue some time ago and it was due to mIRC only listing channels that had prefixes specified in the CHANTYPES token in numeric 005. This limit was removed in recent versions.

I've poked around at this on testnet.

//echo -ag $os $version $md5($mircexe,2) $file($mircexe).sig
XP 7.32 7847343ad9b1ec455154950f051134af ok


//debug -t @a


//quote version

[10:46:01] -> irc.znc.in version
[10:46:01] <- :irc.foobar.net 351 KindOne charybdis-3.5.0-dev(20130616-b2c208b). irc.foobar.net :eHIKMpSZ6 TS6ow 42X
[10:46:01] <- :irc.foobar.net 005 KindOne SAFELIST ELIST=CTU CHANTYPES=# EXCEPTS INVEX CHANMODES=eIbq,k,flj,CFLPQcgimnprstz CHANLIMIT=#:120 PREFIX=(ov)@+ MAXLIST=bqeI:100 MODES=4 NETWORK=foobar KNOCK :are supported by this server
[10:46:01] <- :irc.foobar.net 005 KindOne STATUSMSG=@+ CALLERID=g CASEMAPPING=rfc1459 CHARSET=ascii NICKLEN=30 MAXNICKLEN=31 CHANNELLEN=50 TOPICLEN=390 ETRACE CPRIVMSG CNOTICE DEAF=D :are supported by this server
[10:46:01] <- :irc.foobar.net 005 KindOne MONITOR=100 FNC TARGMAX=NAMES:1,LIST:1,KICK:1,WHOIS:1,PRIVMSG:16,NOTICE:16,ACCEPT:,MONITOR: EXTBAN=$,acjorsxz WHOX CLIENTVER=3.0 :are supported by this server

/list !*

[10:47:06] -> irc.znc.in LIST <10000
[10:47:06] <- :irc.foobar.net 321 KindOne Channel :Users Name
[10:47:06] <- :irc.foobar.net 322 KindOne #happy 3 :Windows ME coming to a computer near you soon...
[10:47:06] <- :irc.foobar.net 322 KindOne #kindone 2 :asdf asdf
[10:47:06] <- :irc.foobar.net 322 KindOne #minecraft 5 :Blocks 'n' shit
[10:47:06] <- :irc.foobar.net 322 KindOne #sigyn 2 :
[10:47:06] <- :irc.foobar.net 322 KindOne #cake 2 :
[10:47:06] <- :irc.foobar.net 322 KindOne # 2 :
[10:47:06] <- :irc.foobar.net 322 KindOne #wumpus 3 :
[10:47:06] <- :irc.foobar.net 322 KindOne #services 21 :I don't always restart services, but when I do, I use telnet. | killall -HUP ircd | alter ircd.conf and enter that killall line. will make ircd re-read conf.
[10:47:06] <- :irc.foobar.net 322 KindOne #annoying 2 :lol
[10:47:06] <- :irc.foobar.net 323 KindOne :End of /LIST

//list !*

Output same as above.

/quote list !*

[10:48:27] -> irc.znc.in list !*
[10:48:27] <- :irc.foobar.net NOTICE * :*** Notice -- OPERSPY KindOne!KindOne@KindOne/.{kindone} LIST *
[10:48:27] <- :irc.foobar.net 321 KindOne Channel :Users Name
[10:48:27] <- :irc.foobar.net 322 KindOne #happy 3 :Windows ME coming to a computer near you soon...
[10:48:27] <- :irc.foobar.net 322 KindOne #kindone 2 :asdf asdf
[10:48:27] <- :irc.foobar.net 322 KindOne #minecraft 5 :Blocks 'n' shit
[10:48:27] <- :irc.foobar.net 322 KindOne #sigyn 2 :
[10:48:27] <- :irc.foobar.net 322 KindOne #cake 2 :
[10:48:27] <- :irc.foobar.net 322 KindOne # 2 :
[10:48:27] <- :irc.foobar.net 322 KindOne #wumpus 3 :
[10:48:27] <- :irc.foobar.net 322 KindOne #services 21 :I don't always restart services, but when I do, I use telnet. | killall -HUP ircd | alter ircd.conf and enter that killall line. will make ircd re-read conf.
[10:48:27] <- :irc.foobar.net 322 KindOne !#meh 1 :
[10:48:27] <- :irc.foobar.net 322 KindOne #annoying 2 :lol
[10:48:28] <- :irc.foobar.net 322 KindOne !##cake 1 :
[10:48:28] <- :irc.foobar.net 323 KindOne :End of /LIST

Works with /quote, as you can see the ! at the beginning of the channel names and that lovely server notice.

Tested 6.34, 7.1, 7.14, They seem to give the /exact/ same output.

Thanks for looking into this. The /list command in mIRC parses the /list parameters to cater for its internal search parameters (those in the list dialog), for servers that have no support for ELIST, and for those that do. So it is not as simple as passing what you have typed to the server.

If you need mIRC to pass exactly what you have typed to the server, due to the server implementing a special format, then /quote will need to be used.

That said, one reason why this is not working may be that the server has not specified that they support wildcard matching in the ELIST token with the M option. If they add the M option to the ELIST token, mIRC should pass !* to the server.

Unfortunately, the ! prefix is a feature of the N option in the ELIST token, which may cause mIRC to parse your request in that way.

I would need to take a closer at the source code to see how the /list command will interpret various combinations of ELIST tokens and parameters to be sure.