On Mon, 2003-10-20 at 23:30, Rimas Kudelis wrote: > Ian wrote: > > > > But if we should use enviroment variables, then just remove all language > > > selections and /charset since they fill no function. > > > > They do for me. _I_ use them to select a different charset on each > > server, and change the charset during runtime. > > yes, they do work. > > > _You_ should use environment variables. > > Why? > so, what I think: > /ccharset is a good command, but the channelname/windowname argument must be > optional (active window should be a default choice), and it should really be > named /wcharset (window charset) and implemented for queries also; > A possibility to set a default IRC charset is a good thing too, but zed does > not want to implement it, and his arguments are the same as David's. But I'm > not going to argue with him in this case, because i don't actually *need* > that feature anymore. Well afair i would be limited the instant .se's utf8 domain names goes online (thats soon or has already happend). It's kinda foolish to not provide one extra list that allows you to set a default language in server commands/channel/queries but still works with utf8 where needed. I assume i could patch it when i have the time, although i don't feel like learning gtk just yet. IMHO it's a really small change since the change on when you use the server window is there, i can't help it if i type /server se3.arcnet.vapor.com faster than i find it i a damn window. (Which also goes for all the other servers i connect to.) -- Ian Kumlien <pomac@vapor.com>
This is a digitally signed message part