Hi Marcus, ] of course not. remove the "-crap -clientcrap" from the line.
You're right... the setting shouldn't have been set to that. I've tried it both ways to no avail. Have you had any success with that? I've already tried it and it doesn't work (with the autolog setting that I mentioned). ] just to make that sure. you run x copies of irssi parallel? and connect ] to different ircnets? That's correct. I have too many servers so I don't want the management hassle of an IRCNet (when using several servers within one client) or loads of config files (when using a different copy for different servers). That's why a CLI parameter to do this would be very nice. In any case... I have my reasons, I just want to know how it can be done :). Having to manage autojoins is too much hassle. All I need is something simple that I can call from the CLI. I don't mind coding it, I just thought someone might have a good pointer into where it should be done. I've looked through the code a fair bit and can't find an easy way of tying in the CLI arguments to an autojoin/autoexecute on the server I called from the CLI. Autoexecute would be preferred, but I'd settle for an autojoin at this point. ] -h/--hostname on the cmdline/as parameter change your local source host. ] e.g. Yes, but this doesn't actually do what it sounds like. If you issue the -h command it doesn't change the line that the IRC client sends when it connects to a server. The USER <USER> <SOURCE> <DEST> :<REAL> line does not appear to be affected. I want to affect the <SOURCE> and <DEST> parameters form the CLI. I've already coded the <SOURCE> with some hacks, but the <DEST> is a bit more of a pain... just looking for pointers here. ] /ircnet add -autosendcmd "msg devel praise you; msg god you suck" yours ] /ircnet add -autosendcmd "msg mom im back; msg dad back to the front" others ] /server add -ircnet yours irc.yourserver.com ] /server add -ircnet others irc.otherserver.com ] /channel add -auto #hell yours ] /channel add -auto #home others I'm looking for a convenient way of doing this from the CLI. Having to manage this will take more time than it's worth unfortunately in a dynamic environment. The reasons are there, I just need a way to accomplish this in an easier fashion. Cheers, -- steve
