1. exwc ed.ex pukes...
- Posted by Brian Broker <bkb at cnw.com>
Mar 01, 2005
-
Last edited Mar 02, 2005
Hi Rob,
I would not recommend using exwc.exe as the default interpreter in ed.bat.
If the default console buffer width is > 80 then ed just "pukes" on XP (as
in "exwc.exw has encountered a problem and needs to close..."). It also
acts funny when the buffer height is greater than the actual window size.
My default cmd screen buffer and window width is usually 100 or more while
my default buffer height is usually 1000 or more. Try those settings and
you'll see what I mean.
I'm tailoring my console lib to address Eu's deficiencies in this area...
-- Brian
2. Re: exwc ed.ex pukes...
- Posted by Robert Craig <rds at RapidEuphoria.com>
Mar 01, 2005
-
Last edited Mar 02, 2005
Brian Broker wrote:
> I would not recommend using exwc.exe as the default interpreter in ed.bat.
> If the default console buffer width is > 80 then ed just "pukes" on XP (as
> in "exwc.exw has encountered a problem and needs to close..."). It also
> acts funny when the buffer height is greater than the actual window size.
>
> My default cmd screen buffer and window width is usually 100 or more while
> my default buffer height is usually 1000 or more. Try those settings and
> you'll see what I mean.
>
> I'm tailoring my console lib to address Eu's deficiencies in this area...
Thanks. 2.5 official is frozen, but I'll look into this eventually.
Maybe I'll learn something from what you are doing.
If enough bugs are reported, I can always have a 2.5.1 release.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: exwc ed.ex pukes...
Robert Craig wrote:
>
> Brian Broker wrote:
> > I would not recommend using exwc.exe as the default interpreter in ed.bat.
> > If the default console buffer width is > 80 then ed just "pukes" on XP (as
> > in "exwc.exw has encountered a problem and needs to close..."). It also
> > acts funny when the buffer height is greater than the actual window size.
> >
> > My default cmd screen buffer and window width is usually 100 or more while
> > my default buffer height is usually 1000 or more. Try those settings and
> > you'll see what I mean.
> >
> > I'm tailoring my console lib to address Eu's deficiencies in this area...
>
> Thanks. 2.5 official is frozen, but I'll look into this eventually.
> Maybe I'll learn something from what you are doing.
> If enough bugs are reported, I can always have a 2.5.1 release.
Does this mean that there could eventuly be more frequent releases?
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
>
CoJaBo
"Error: Keyboard not present.
Press F2 to continue, F10 for setup." -- Old 486
[1010] << Supposed to be a computer
QWERTY <<
Win XP SP2 Laptop
Athlon 64 3700+ 2.4Ghz, 2GB RAM, 100GB HDD,
NVIDIA GeForce4 440 Go 64M Video card,
1920x1200 Resolution LCD
Bl@ckf|re has invaded this signuture! Star: Got mustard?(tm)
Bl@ckf|re has invaded this signuture! Star: Got mustard?(tm)
4. Re: exwc ed.ex pukes...
CoJaBo wrote:
> Does this mean that there could eventuly be more frequent releases?
I'd like to do more frequent releases, but there's a lot of overhead
in doing a release, so I need to accumulate a certain minimum
number of bug fixes or new features to make it worthwhile.
Also I think it's better to have a relatively big change
infrequently, than to have a constant stream of tiny changes,
where everyone seems to be using a slightly different version,
and bug reports are harder to investigate. I must admit I've spent
too long in going from 2.4 to 2.5. I really shouldn't take more
than a year between official releases.
If I get some significant bugs in the first couple of months,
I might do a 2.5.1 release.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
