(In reply to comment #7)
> (In reply to comment #6)
> > The normal way to list channels in a dedicated IRC client like irssi is with
> > "/list PATTERN", which lists channels matching PATTERN (which is a shell-style
> > glob, I think?).
>
> Actually, this isn't how this works: LIST only supports specifying a single
> channel name, to get its number of occupants and topic (or an error if it
> doesn't exist).
To further muddy the waters, a large number of server variants actually do support listing with wildcards. Thankfully, there is a recognised detection mechanism to find out *if* it is supported: RPL_ISUPPORT (005)'s ELIST token. (I'm not certain *everything* uses this, but if it doesn't, well... bad luck for them?)
(In reply to comment #7)
> (In reply to comment #6)
> > The normal way to list channels in a dedicated IRC client like irssi is with
> > "/list PATTERN", which lists channels matching PATTERN (which is a shell-style
> > glob, I think?).
>
> Actually, this isn't how this works: LIST only supports specifying a single
> channel name, to get its number of occupants and topic (or an error if it
> doesn't exist).
To further muddy the waters, a large number of server variants actually do support listing with wildcards. Thankfully, there is a recognised detection mechanism to find out *if* it is supported: RPL_ISUPPORT (005)'s ELIST token. (I'm not certain *everything* uses this, but if it doesn't, well... bad luck for them?)
See: http:// www.irc. org/tech_ docs/005. html
Basically, you want to look for 'M' in ELIST's value if I remember rightly.