Re: [Amsn-devel] Auto-resize display pictures

2006-01-20 Thread Jérôme Gagnon-Voyer
I would have written a shorter letter, but I did not have the time.Blaise PascalAdd that to your signature Youness!Le 18 janvier 2006 à 17:41, Youness Alaoui a écrit :sorry.. its either writing long emails to you (inconito:P) or studying Cobol for my next project... what would you decide? :P

Re: [Amsn-devel] amsn forums administration

2006-01-20 Thread Youness Alaoui
my answer to Yves : Yves, get me Administrator status, don't forget the contract, we decided to use amsn.recordingground.com as our primary forum site to the ONE CONDITION that amsn admins are also forum admins, I'm the main amsn administrator, so I ask for admin status..I've wasted a whole

Re: [Amsn-devel] URGENT : Fwd: SourceForge.net Support: High ViewCVS usage for your project

2006-01-20 Thread Youness Alaoui
exactly.. we have no limit on http, but on viewCVS, it's a bad thing.. because viewCVS is a script that calls the cvs command each time.. we don't care about the bandwidth, what we care about is the CPU usage.. if we have 100 000 'cvs' commands executed per second, you can be sure SF servers

Re: [Amsn-devel] URGENT : Fwd: SourceForge.net Support: High ViewCVS usage for your project

2006-01-20 Thread Frédéric
Hi Youness's idea seems to be the right things to do, and that's also what I was thinking of. As Jerome proposed, I can take care of updating the plugininfo.xml. If I understood well, we have no limitation for http. So if I put plugininfo.xml files into the CVS in the "www" part, and ask the

Re: [Amsn-devel] amsn forums administration

2006-01-20 Thread Youness Alaoui
haha, stupid me (and especially Yves).. I forgot that, as a moderator, I have access to a button on each post, called "IP".. and this is the result when I click on IP for backp2 : IP address for this post 65.50.164.147 [ 10 Posts ] [ Look up IP address ] Users posting from this

Re: [Amsn-devel] amsn forums administration

2006-01-20 Thread Youness Alaoui
no, I don't have shell access, and it's not possible, but it's BBCode, so we can extract it ourselves...we don't need ryves to extract it.. all we'll need after that is to configure it.. might need some work... but let's just hope Yves will collaborate.. if he doesn't, we'll have a lot of t

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
Sorry. I haven't accused anyone of anthing that I'm aware of. If it came across that way, I apologize. As I expalined to Vivia, I left eliminating font paths to the weekend, because I won't have the time to do that until then. It's not a matter of sloth, but rather of time management. Other po

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Youness Alaoui
you "fucked up" your system, it is being vulgar, but not rude, I didn't say fuck you, I didn't insult you in any other way, I wasn't rude with you, so being vulgar doesn't mean being rude, but I won't argue with you on that because it seems your so stupid, you won't understand what I'll be

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
Actually, I never inisted on not removing fonts from xorg.conf. I just haven't gotten around to it yet. (Basically because of the time involved in commenting them out one by one and relaunching the server each time.) It's on my to-do list for this weekend. On 1/20/06, Vivia Nikolaidou <[EMAIL P

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
http://mercea.net/~exmh/html/exmh-users/2005-01/msg6.html (search the thread for the solution that this guy found) http://www.tldp.org/FAQ/faqs/Wine-FAQ Adding the locales wasn't the only solution I had suggested. In the FAQ it is suggested to remove your font paths from xorg.conf , which y

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
Quite true (about vulgarity and rudeness). However, there is no way to be vulgar without being rude. I'm now talking to some tcl folks about this. Their first stab at it is like this: Run 'xrdb -remove' from the shell prompt, then try launching amsn. If it comes up with no errors, that's goo

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
On Fri, 20 Jan 2006, Gerald Britton wrote: > hmmm...interesting. Well I consider profanity to be rude, every time, > all the time. If you are vulgar, then you are rude, no second > thoughts about that. Being vulgar is not the only way to be rude. Sometimes you can be a lot worse without using

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
Thanks! On 1/20/06, Vivia Nikolaidou <[EMAIL PROTECTED]> wrote: > > > Now I would very much like to pursue this issue with the tk group. > > Can anyone point me in their direction? > > http://www.tcl.tk > > > --- > This SF.net email is sponsored

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
hmmm...interesting. Well I consider profanity to be rude, every time, all the time. If you are vulgar, then you are rude, no second thoughts about that. I have carefully maintained my machine (no screamer to be sure, just a 1gig with 384M ram) on a gentoo distro for several years. Following gen

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Youness Alaoui
1 - you were rude, no second thoughts about that 2 - what profanities from "the previous poster" ???* 3 - I prefer to be vulgar when needed than to be rude when not needed.. it is said that being polite is simply another way of being hypocrite 4 - frustration should go to : a) your mach

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
> Now I would very much like to pursue this issue with the tk group. > Can anyone point me in their direction? http://www.tcl.tk --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download t

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
My apologies to those who feel that I answered harshly. I suppose my frustration came through. At least I did not resort to profanities in the manner of the previous poster (I do not use such profanity in my speech and certainly not in writing. It is simply not appropriate.) I am also quite th

Re: [Amsn-devel] Inks.... :( (Depressive people don't read that :p)

2006-01-20 Thread Youness Alaoui
humm.. I remember doing it more than once with the old MSN version and the plugin... you could send a screenshot in ink it would be in png I think... not sure anyways, maybe there's a way to do that, we'll have to check! (a copy image to clipboard->paste, a custom smiuley, drag drop in handwri

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Youness Alaoui
I'm a bit surprised by the 'harshness' of this thread... let me summarize it : 1 - a user fucks up his PC and asks for help 2 - we try everything to help him as much as possible 3 - it didn't work 4 - we found out his pc is not 'normal' and ask him to install what HAS to be installed 5 - he clea

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
fyi -- I suppress all the other locales to mamke glibc compile faster (much, much faster actually) On 1/20/06, Vivia Nikolaidou <[EMAIL PROTECTED]> wrote: > > Did that by running amsn like this: > > > > LC_ALL=en_US amsn > > > > I also tried > > > > LANG=en_US amsn > > > > Here's the outp

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
On Fri, 20 Jan 2006, Gerald Britton wrote: > amsn must respect the locale I set (via LC_ALL= or LANG=). It has no > business trying to use any others. At the very least it should query > locale availability (locale -a) before trying to use them. it's not amsn, it's tk, i repeat :( > "J

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
amsn must respect the locale I set (via LC_ALL= or LANG=). It has no business trying to use any others. At the very least it should query locale availability (locale -a) before trying to use them. "Just giving it a try" will, in my case, result in an eight-hour compile job to try to circumvent a

Re: [Amsn-devel] URGENT : Fwd: SourceForge.net Support: High ViewCVS usage for your project

2006-01-20 Thread Youness Alaoui
hehe.. yeah, calm down :P anyways, as Is aid, we'll still have probs with lang files, but for plugins, we can correct this, ASAP : as I said before, all we need to do is to change the URLS in plugininfo.xml and add urls for the plugins that don't have any... here's the answer I received from

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
On Fri, 20 Jan 2006, Gerald Britton wrote: > Definitely. Why spend time compiling locales (hours and hours on my > machine) that I won't use? ... what if aMSN is trying to use them now? OK, I don't know, just give it a try > > On 1/20/06, Vivia Nikolaidou <[EMAIL PROTECTED]> wrote: > > On Fri

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
Definitely. Why spend time compiling locales (hours and hours on my machine) that I won't use? On 1/20/06, Vivia Nikolaidou <[EMAIL PROTECTED]> wrote: > On Fri, 20 Jan 2006, Gerald Britton wrote: > > > fyi -- I suppress all the other locales to mamke glibc compile faster > > (much, much faster ac

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
On Fri, 20 Jan 2006, Gerald Britton wrote: > fyi -- I suppress all the other locales to mamke glibc compile faster > (much, much faster actually) are you sure this is a good idea? :) --- This SF.net email is sponsored by: Splunk Inc. Do you gr

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Vivia Nikolaidou
> Did that by running amsn like this: > > LC_ALL=en_US amsn > > I also tried > > LANG=en_US amsn > > Here's the output from my locale command: > > $ locale -a > C > POSIX > en_US > en_US.utf8 Where are all other locales?... Anyway, try LC_ALL=en_US.UTF-8 , though I don't think that

Re: [Amsn-devel] error messages during signon

2006-01-20 Thread Gerald Britton
OK -- I took the instructions from the FAQ: "First of all, it may be a font problem: try making aMSN run with a different font (under Tools -> Preferences -> Appearance). " Did that, Changed it to Arial, 10 pt "Second, you may need to run aMSN from a different encoding (under Tools -> Preferen