RE: FW: January IVCUG Meeting

2000-01-16 Thread Chen Shapira
> heh... is this the right place to mention VI stands for > Visual Interface > (of ex)? :-) no kidding? and here I was thinking that VI is visual intercal... everyone who can write a telnet client in intercal, stand up! Chen Shapira [EMAIL PROTECTED] print pack"C*",split/\D+/,`echo "16iII*o

RE: FW: January IVCUG Meeting

2000-01-16 Thread Ira Abramov
On Sun, 16 Jan 2000, Chen Shapira wrote: > > no. you'll find it extremely hard to convert a VC++ > > programmer into using > > linux. > > agreed. the otherway around too. > after years of programming with vi, I find it difficult using visual > anything. heh... is this the right place to menti

RE: FW: January IVCUG Meeting

2000-01-16 Thread Chen Shapira
> and seemingly-commercialized? i'd prefer to leave the LUG's > state as is, > for internal meetings. commercialization is vaiable only for > bringing up > events that cannot be set up in a completely vulentary > environment (e.g. a > linux booth at some expo...). I don't suggest commercial

Re: FW: January IVCUG Meeting

2000-01-13 Thread Uri Bruck
On Thu, 13 Jan 2000, guy keren wrote: > > btw, as for celebrities - this is fun once or twice, but eventually, it > tends to be repeteteive, and boring. not to mention one great disadvantage > - they carry out the talk in english, and this makes it less fluent then > it could be, when done in h

Re: FW: January IVCUG Meeting

2000-01-13 Thread guy keren
On Thu, 13 Jan 2000, Chen Shapira wrote: > few points: > > 1. Note how well orginized and proffesional our window collegues are. and seemingly-commercialized? i'd prefer to leave the LUG's state as is, for internal meetings. commercialization is vaiable only for bringing up events that cannot