Hi,
I am trying to use tkabber on Slackware Linux 9.1. Everything seems OK, but I do not see my roster in the left part of the Tkabber window. The roster is imported OK, when people write to me, I see their nicks. It is also possible to export the roster into the file. Could you tell me what should I write into the config.tcl file?
Thank you Jakub
Hiden roster
This is the first time I read something like this.
roster
Hi,
roster is not hidden by Ctrl+R, I see the window for him, bu it is completely white, without any text. I have tried Tkabber 0.9.6 (beta), 0.9.7 and Starpack, everything with the same result, both with tabbed and untabbed mode. I am sending the error message:
can't read "jidsingroup()": no such element in array
can't read "jidsingroup()": no such element in array
while executing
"lrmdups $jidsingroup($group)"
(procedure "roster::redraw" line 137)
invoked from within
"roster::redraw"
(procedure "client:roster_cmd" line 5)
invoked from within
"client:roster_cmd 1 END_ROSTER"
("uplevel" body line 1)
invoked from within
"uplevel #0 "$cmd $connid END_ROSTER""
(procedure "::jlib::parse_roster_get" line 71)
invoked from within
"::jlib::parse_roster_get 1 0 client:roster_cmd OK {query {xmlns jabber:iq:roster} {{item {subscription from jid icq.jabber.cz/registered name {ICQ Tra..."
("uplevel" body line 1)
invoked from within
"uplevel \#0 "$cmd OK [list [lindex $children 0]]""
("iq" arm line 29)
invoked from within
"switch -- $tag {
iq {
set useid 0
set id ""
set type [wrapper:getattr $vars type]
if {[wrapper:isattr $vars id] == 1} {
set ..."
(procedure "::jlib::parse1" line 25)
invoked from within
"::jlib::parse1 1 {iq {from kseles@jabber.cz/tkabber id 2 type result} {{query {xmlns jabber:iq:roster} {{item {subscription from jid icq.jabber.cz/reg..."
("after" script)
I am not a programmer, so I do not understand perfectly, but it is possible, that the problem is not at the side of tkabber.
Thank you
Jakub
Problematic character
It seems to complain when trying to draw icq-t or similar. Now that you mention, I remember that a lot of month ago (when I used transports) an error similar ocurred to me when a contact in other network used a nick with a strange character.
You can try this:
If this is the case, you have three solutions:
It might be the case when nes
It might be the case when nested roster is used and some group name has :: (value of options(nested_delimiter)) at the very beginning.
Workaround: Don't use nested roster.
Hope it will be fixed soon.