Closed Bug 180873 Opened 22 years ago Closed 21 years ago

ChatZilla doesn't remember different nicks

Categories

(Other Applications :: ChatZilla, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: drepper.fsp, Assigned: rginda)

References

Details

When connected to multiple IRC server one can choose different nicks and
ChatZilla handles them correctly.  But when joining a new channel (or re-joining
an old one or restarting Mozilla overall) the nich selected with the last /nick
command is used for all servers.  ChatZilla should instead remember the nicks
for each server separately.
*** Bug 202873 has been marked as a duplicate of this bug. ***
This has become worse in the meantime, since CZ supports auto-reconnect now but
doesn't use the nick one previously used for this server.

E.g. I'm using nick 'dbachran' on freenode and 'g0ph3r' on moznet. When I get
disconnected on moznet, CZ reconnects and reopens all channels I have been in,
but my nick is 'dbachran' instead of 'g0ph3r'.
I've been told to solve this with some JS hacking similar to

 http://www.hacksrus.com/~ginda/chatzilla/chatzillarc.js

My JS-fu isn't strong enough to do this without lots of reading of the CZ
sources so I didn't do anything.  If somebody with more insight into these
issues can post a receipe the urgency to get a complete solution might be reduced.
the hack is:

client.networks["moznet"].INITIAL_NICK = "g0ph3r";
client.networks["freenode"].INITIAL_NICK = "dbachran";

Just put that in a a .js file, and add it to the startup script pref either via
the pref panel, or by typing /eval client.INITIAL_SCRIPTS =
"file:///path/to/foo.js" in chatzilla.
Status: NEW → ASSIGNED
Depends on: 210744
The chatzilla 0.9.x branch has landed on the trunk and should be available in
tomorrow's nightly build.  If you believe this bug has not actually been fixed,
please repoen it.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.