This is just a little (imho commonsense) suggestion for the IAL. If I type /userhost somenick, somenick should be added to the IAL. If doing a /who #chan updates the IAL, why shouldn't doing a /userhost add that user as well? It seems logical to me and I'm sure it wouldn't be too difficult to add.

Are you referring to a nick that shares no common channels with you on that cid? When should that entry be removed from the IAL?

I like the idea, though. I've always wanted something similar to $ialchan, like maybe $ialmsg for those folks you have query windows open to or who have msg'd you, perhaps garbage collected by a command like /ialmsg -g to clean out all but the currently open queries. I'm not too sure how that would work with a single-query window, since I've never used that option.

Regarding the $ialmsg, how exactly should it be? If it's going to contain only the nicks that have opened a query window with you AND are on a common channel with you, I wouldn't mind. However, I'm not sure whether it should be added for all nicks that have a query window (regardless of whether they share a common channel with you), since the integrity of this list would be in danger. You can be sure about $ial, $ialchan and even $ibl's integrity because there is no way that a user would change their address (or be banned/unbanned) without letting you know (by the QUIT or the MODE message respectively, which are only sent when you share a common channel with the nick). If a nick stored in $ialmsg's list does not share a common channel with you and they quit and then reconnect with a different address, $ialmsg(<nick>) would hold the old address. There is a $query().addr identifier, which returns the address of the nick, but the help file warns you that it might not always be correct.

$query($nick/N).addr covers half (the half with the open query windows) of what I would envision $ialmsg, but doesn't cover those nicks who've msg'd you or those that you've /msg'd and not /query'd. And I do realize that the entire $ialmsg would inherently be unreliable.

If you're talking about users who share a common channel with you, its' already working fine: /userhost adds the person to the IAL. If those nicks are not on a common channel, IAL shouldn't have anything to do with them, since by definition, IAL holds "all users who are currently on the same channels as you."

Use an ugly mug /watch or /ison technique

Well I agree with your $ialmsg suggestion, though thats not what I'm talking about. What I mean is I join #chan, and there is User (who is already on the chan). If I do //echo -a $ial(User,1) I get $null. Now if I type /who User then //echo -a $ial(User,1) then I get the user's hostname. Meaning if the user is on the channel and I /who them, mIRC adds the user to the IAL. Also mIRC adds the user to the IAL if you /whois them. So if /whois and /who add the user to the IAL, why shouldn't /userhost as well?

Have you read my post or you chose to ignore it? It is working fine here, I tested it on different networks and /userhost adds the person to the IAL, just like /who and /whois do.

Besides, item 11 of 5.91 versions.txt clearly states:
11.Fixed /userhost not updating IAL.

Well I'm using 6.03 and it's not updating it for me...

works fine here..
maybe u have a raw event (302) that /ialclear every time it gets the ial from /userhost

Umm no I don't. I never said the IAL got cleared, I said that the user I did a /userhost on wasn't added. Other nicks are still in the IAL.

i didn't mean just /ialclear, i meant /ialclear USER
anyway, try to /remote off and then try it.. if it still doesn't work so i dunno.. i checked it here (6.03 too) and it works fine.

Hmm now all of a sudden it's working fine (even with remotes/raws on), I must have just been doing something wrong...