* FORMAT_KILL You have been killed by $1 on $2 [$3-] displays as: You have been killed by ewheat.org!BarK0de [(erp)] $1 should have nick and server seperated into two different variables. $1 should give nick, $2 should give server, $3 has the reason without the brackets. /showsplits doesnt work. If it does what I think it does (show which servers split) open a window, /query a user, kill the window, and all the messages from that user appear to go to /dev/null (: <_shade> [>] [mailbox] On MAIL from "* *" do @ :xx = restw(1 $pipe(grep From: $getenv(MAIL) | tail -1));beep;xecho -b new email has arrived${xx ? [ \(from \"$xx\"\)] :}. [SILENT] <0> panasync: speaking of tab completion, if you're talking with someone in msgs and then do a /dcc send beginning_of_nick it completes that to /m nick , which is kinda annoying 6 [vim(~dem0n@shell.planetc.com)] i've got a bug here... in bitchx 75p2-10, when you have operview on +hide, and do /eval echo $winbound() it seg faults noun: /stack push set lastlog_level ; /set lastlog_level off ; /stack pop set lastlog_level that /set in the middle also turned off window lastlog_level for the current window only and the /stack pop doesn't revert that to the original setting 5 [MHacker(mhacker@ip209.st-catherines2.dialup.canada.psi.net)] btw we found a bug. 4 [MHacker(mhacker@ip209.st-catherines2.dialup.canada.psi.net)] :cls-tot!TotalMON@dsle01157.adsl.teleusplanet.net PRIVMSG #*.psi.net :PING 916974436 3 [MHacker(mhacker@ip209.st-catherines2.dialup.canada.psi.net)] BitchX ignores it 2 [MHacker(mhacker@ip209.st-catherines2.dialup.canada.psi.net)] ... [4] <- [:habitais!habit@cx61788-b.dt1.sdca.home.com NOTICE panasync_ :KNOCK: #habit (habitais [habit@cx61788-b.dt1.sdca.home.com] has asked for an invite)] -habitais(habit@cx61788-b.dt1.sdca.home.com)- KNOCK: #habit (habitais [habit@cx61788-b.dt1.sdca.home.com] has asked for an invite) [4] <- [:Phucilag_!phucilag@p115.access1.cvg.choice.net NOTICE panasync_ :INVITE: #habit (Phucilag_ invited Phucilag [phucilag@p115.access1.cvg.choice.net])] -Phucilag_(phucilag@p115.access1.cvg.choice.net)- INVITE: #habit (Phucilag_ invited Phucilag [phucilag@p115.access1.cvg.choice.net]) 2 [daedo(nate@buxton-19.ime.net)] if you use %S more than once in status_server it segfaults 1 [daedo(nate@buxton-19.ime.net)] dunno if it does it with the other status_ vars sellfone (Mar 3 07:02): those fuckers changed it again 2.8/hybrid-6b48 i do /mode #channelimnotinbutexists -o anything and get odd server stuff instead of the real messages. damned ircd ;) 0 [kendoggie(~kenny@async02.li-rt-03.lightning.net)] i know you're not there but i have a question.....i'm running bitchx win95..it doesnt recognize where the help file is. Prob 2. When i'm typing the apparnce of teh letters is behind to that which i am typing..in mirc i'm seeing the letters as i type..in bitchx i dont see them right away..sorry if it doesnt make sense..also to send i have to hit enter more than once. thanks for you help.. kenny@typhoon.lightning.net lwk doesn't leave the channel. [pod(pod@486.org)] if your connected to two servers, and do a /exec /dcc or /dns, the output will be in the first window, not the window that your on, its annoying for me =) [RoboHak(RoboHak@we-24-130-69-150.we.mediaone.net)] on -notice * {^set input_prompt %K!%n$T%K! %n} [RoboHak(RoboHak@we-24-130-69-150.we.mediaone.net)] then /notice yourself panasync: if your in window 1 and do alt+2, an /echo will go to window 1 but if you do alt+2 twice it'll then go to window 2 indigoid scr-bx doesn't work under solaris. whether to screen the session like screen would or kill it like if you're logged in to a shell and your isp drops you have it on kill by default though default would be to kill it pretend doesn't work from a hook. /pretend :Dianora!db@propane.tank.edu PRIVMSG timer :oooo 5 [amf(~amf@rb187.isis.de)] two bugs in 1.0c8: 1) "xecho -c" doesn work ... i got it in ON PUBLIC, and it still outputted to the channel-window. workaround with "xecho -win $winnum()". 2) the userlist seem to double the entries on every /SAVE .. 4 [amf(~amf@rb187.isis.de)] both bugs where already in the first 1.0, and both worked perfectly in 75p3. .