[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Get IP from server, 16 tab limit, xchat_hook_print() issue



I'm going to wrap several replies into one message here to avoid wasting
bandwidth.

Peter Zelezny wrote:
>* xchat doesn't support this "connecting from xxxx" line. Is that a new
>  non-rfc numeric?

While some sources incorrectly attribute it to RFC1459, it wasn't around at
that time.  (In the early 90s there was no need to mask hostnames, and it's
perfectly reasonable that they never even considered this.)  In Unreal's case,
it's an RPL_WHOISHOST, which is a raw 379.  I think Bahamut/ircu -- and
probably the rest of that fork -- use 338, RPL_WHOISACTUALLY.  But these are
"new" only in relation to RFC1459; they've been around for ages.

I wasn't aware that XChat doesn't support this numeric.  A number of clients
support RPL_WHOISHOST (and RPL_WHOISACTUALLY).  mIRC has since last year for
example, and jIRC -- the Java applet-based client from JPilot -- has for at
least two years.  I presumed that XChat did, as well.  Mea culpa.

I suppose the question would be whether native support for non-1459 numerics
is warranted, or whether it should be handled by plugins.  (By the way,
"tclplugin" for XChat lists raw 378 in its documentation --
http://www.scriptkitties.com/tclplugin/tclplugin.shtml -- see "Name: on -
Execute a command on an irc event").  FYI, a fairly comprehensive raw listing
is available at http://www.irc101.org/numerics/ -- it includes a number of
IRCD-specific ones.

Peter Zelezny wrote:
>* The current implementation uses a blocking DNS lookup. It was assumed
>  most people wouldn't use it, so the few who do have to put up with the
>  pain of a quick lockup.

Well, if "quick" is the operative word, I can't imagine this being much of an
issue.  But, point taken.

Peter Zelezny wrote:
>* I think most people have a "proper" routable IP address and don't want
>  this ON.

Hehe  Survey time!  :o)

Seriously: Thanks for the additional information.  As I mentioned in another
email, I'm VERY new to XChat, and still learning my way around.  I appreciate
everyone's patience as I come up to speed.

On the subject of a 16 tab limit, Peter Zelezny wrote:
>No, there is no limit. I don't know where you got this idea from. Are you
>getting the "< >" scrolling buttons when you open tabs that don't fit
>anymore?

No, I'm not, and that's where I got the idea. :o)  I just started joining
channels to see if I hit a wall, and at 16 tabs I apparently couldn't open any
new ones.  I was opered at the time, so it wasn't an IRCD-side limit (most
networks limit the number of channels you can join, of course).  No scrolling
buttons appeared.  A 16 tab limit did NOT make sense, which is why I went
looking through the headers and eventually asked here.

Anthony A. D. Talltree wrote:
>They sometimes don't work unless one does
>
>/set inputgad_superfocus 0

Thanks for the input, Anthony.  I'll play with this and see if that's what was
throwing me.  If I can't get it to work I'll check in again.

Finally: I stumbled across something in the plugin hook code that I wanted to
highlight.  When "Colored nicks" is set, xchat_hook_print() callbacks receive
the opening nick color code before the nick in word[1].  Maybe this was
intentional, but I thought I should mention it -- I was expecting just the
nick.  Can I get a clarification on whether this is a bug or intentional?

Thanks for a great client... to everyone who has contributed!

Cheers,
James


--
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/