Forums Bug Reports /list unable to halt ?

after the /list command I am unable to remove the following text from the status window:

Listing channels
End of /List

I thought I could silence this by using /.list but that dind't work either.

The line reading 'End of /List' is raw 323, in my raws.mrc i have :

raw 323:*: { halt }

Anyone had this problem before, is there a solution or is this a bug? Please help.

Hm, indeed, doesn't work here either.

Confirmed.

It's been like this for as long as i can remember, i took it as an unsilencable thing like alot of the others built into mIRC, so i personally think it's not a bug.

From the new mirc 6.17 versions .txt :

6.Fixed /.uwho message not being hidden.

That would be an example of one of the commands that could not be silenced before but it was fixed in this version. It is strange that /.uwho would be fixed and not /.list .

To clarify, I don't see why /.list not working would be a bug, the /.uwho message not being hidden was an mIRC message that wasn't hiding, whereas the End of List message is a server one. Much the same as why /.whois doesn't silence anything either.

What I think is a bug however, is the fact that using a raw event to halt it doesn't work. I would have thought it should.

Regards,

/localinfo -u
Local host: host86-131-83-216.range86-131.btcentralplus.com (86.131.83.216)

That's not silenceable.

Yes it is.

You can't silence it when you connect, or script around it like a normal silenceable command though can you? that's my point.

Neither is * Connecting to server.server.com (6667)

No, but /.localinfo (when actually executed manually, rather than when you get the message on connct), is silenceable.

This is kind of irrelevant anyway. You're talking about internal mIRC commands, whereas /list triggers server messages and doesn't return any so-called "mIRC messages". You should be able to halt raws 321 and 323, unless there is some technical limitation I don't know of.

By the way, it appears this has been reported before.

Regards,

You're wrong, i opened mIRC with a resource editor and

Listing channels
End of /List

exist within mIRC, they don't come from the server.

ok so it looks like we should be looking out for a fix relating to this raw in future version of mIRC. Thanks for everyones help.

That doesn't mean the server doesn't send a raw, and they should be silenceable through /halt. After some discussion with a couple of other experienced mIRCers, some logic problems have arisen which might explain why 321 isn't haltable in the first place.

Being able to block 321 would also block the creation of the channels list window. However, 322 would still be received, so what should mIRC do with the information? The only reasonable solution to this would be to move the creation of the list window to raw 322, so if you /halt 322 it stops the list window being created. However, the problem with this is, if you did /list >1000 on a small network, or /list #channelname which is +s, no /list window would be created at all despite expecting one to be. Also, if you only want to receive the last channel to be listed you would be waiting ages, and then the window would be created after typing /list.

This doesn't explain why 323 can't be halted however, and I don't see why it shouldn't be if that's what people want to block the message appearing.

By the way, please don't worry about posting a bunch of possible solutions We'll see what Khaled thinks in upcoming versions I guess!

Regards,

I agree, it would be good to silence those messages, i just did a check though, mention it if i didn't spot it, but i didn't see a raw for 'Listing channels' in the debug window.

I think it might be that.

halting 323 works fine its just 321 that is messing up.

Any display of info should be haltable, even if the internal processing of the raw MUST take place. I see no reason why the messages in the status window need be displayed.

On a different note all together, what would solve alot of these problems was if we had a savebuf/loadbuf option, that allowed you to save the defualt line color of each line, even if its just a ctrl-k##, that either is left as that when reloaded or processed into the default color of the line (like how filter has -z now), then we can just edit out what we dont want and loadbuf the window back up. :-)

If you want to stop the /list command use "/raw -q list"

no, my original post was to halt what text was echo'd in status after the /list command.