|
|
|
Joined: Feb 2003
Posts: 806
Hoopy frood
|
Hoopy frood
Joined: Feb 2003
Posts: 806 |
When doesn't it work? I've never found myself in such situation..
|
|
|
|
Iori
|
Iori
|
It works that way all the time here.
|
|
|
|
Olathe
|
Olathe
|
According to RFC 2812, IRC servers are supposed to interpret joining 0 (not #0) as parting all channels. This is not a client feature, which can be seen by looking at mIRC's debug output; mIRC doesn't send a part message, it sends "JOIN 0". Commas separate channel names in a join message, so the second channel name in JOIN #1,000 is 000.
|
|
|
|
Joined: Feb 2003
Posts: 2,737
Hoopy frood
|
Hoopy frood
Joined: Feb 2003
Posts: 2,737 |
There.. Is.. Nothing.. To.. Fix...
The... observed... behavior... is... intended...
People..... need..... to..... read..... harder.....
Well. At least I won lunch. Good philosophy, see good in bad, I like!
|
|
|
|
Joined: Jan 2003
Posts: 2,973
Hoopy frood
|
Hoopy frood
Joined: Jan 2003
Posts: 2,973 |
Iori: It does to an extent. If you click on "#somechan,0" or "#somechan,#another" you will only join #somechan.
I was actually basis that post off what Iori said. The fact that clicking on the #1,0 will join 0 also, just $comechan,0 will join #somechan. I was testing it out, and the only reason it works is because most users tend to click a link in the cente. Being there is a 0 in the center of the link, it joins the 000 side fo the comma. ( #1,000)
|
|
|
|
Joined: Feb 2003
Posts: 806
Hoopy frood
|
Hoopy frood
Joined: Feb 2003
Posts: 806 |
Well it doesn't join 0 also.. actually here it doesn't join any other channel than the first one specified.
|
|
|
|
Iori
|
Iori
|
The fact that clicking on the #1,0 will join 0 also It doesn't. It ALWAYS joins the first channel listed (based on the comma as delimiter) just as I said, and as you quoted, If you click on #1,0 you will join #1, if you click on #1,000 you will join #1 - no matter where on the string you click. NEVER will mIRC join "000" from a double click, unless you have scripted #channel hotlinks, in which case it is not mIRCs fault.
|
|
|
|
|
|
|
|