1. ee bug
While I'm at it, I might as well report a bug I found in the ee editor.
This only happens on my old 486 notebook (ok, don't laugh. I hardly ever use
it, but I will report a bug anyway). I pressed ctrl+c to copy some text and
the program terminated with a ^c on the screen. I knew what was happening,
so I added the line
allow_break(0)
at the top of ee.ex. that only stopped the program terminating, it didn't
stop the ^c comming up on the screen. this is very annoying (or it will be
if I ever use that puter again) as i had to use the edit menu. It is using
windows 95.
Daryl
2. Re: ee bug
Howdy!
> While I'm at it, I might as well report a bug I found in the ee editor.
> This only happens on my old 486 notebook (ok, don't laugh. I hardly ever
use
> it, but I will report a bug anyway). I pressed ctrl+c to copy some text
and
> the program terminated with a ^c on the screen. I knew what was
happening,
> so I added the line
>
> allow_break(0)
>
> at the top of ee.ex. that only stopped the program terminating, it didn't
> stop the ^c comming up on the screen. this is very annoying (or it will
be
> if I ever use that puter again) as i had to use the edit menu. It is
using
> windows 95.
>
> Daryl
It's not your 486. I've noticed this occurring also on my Celeron WinME
system.
-- Travis --
3. Re: ee bug
Daryl wrote:
> I pressed ctrl+c to copy some text and
> the program terminated with a ^c on the
> screen.
Is this EE, or EE:CS?
EE should never see the Ctrl+C keystroke. Before reading the key buffer, it
first checks for a Ctrl+C. If there is on in the buffer, it clears the
buffer, so it's never actually read by Euphoria.
Perhaps the BIOS on you machine is a bit different? I don't really have a
good answer for this.
-- David Cuny
