Nick Holland <nick <at> holland-consulting.net> writes: > > Does it make sense to add features to EPIC4? Scripts that depend on epic4, epic4 and epic5 do not have compatible interfaces > > There's a nasty bug in EPIC4 which causes epic to hang and spin the > CPU when you resize its terminal window. Found it to be very annoying > for most of my users, and required a "kill -9" to free up my CPU. Perhaps this is related to the 'don''t compile with -O2' advice that the website gives. What arch is this on? Did you try this patch or my previous one forcing a lower optimisation level? I've never experienced the problem you describe.
> > Apparently, this is a known issue with the last version of epic4, the > known solution is to upgrade to epic5. I googled for this problem and your report here was my only substantive hit, and #epic is too busy discussing bad cops/good cops to answer questions, heh. Also, the mailing list archives seem to have gone 404, do you have a link? > > I did a compile-from-source of epic5 and it seems to work, though I'm > a very simplistic epic user, so everything that doesn't work as I did > in epic4 I'm assuming is a difference with epic5, and my "it works" > consists of "it talks, it doesn't hang, and my users can resize their > window without flinging profanity at me". I have yet to find a decent epic5 script, is bare epic5 usable? Otherwise I'd have worked on an epic5 port, but epic4 is the second thing I install from ports on any machine I use and when the latest update triggered 'random bug' (^C hanging epic instead of letting me use colours) with -O2, I posted my patch (after speaking to the denizens of #epic), and then I found a need to have perl support (which is basically free since perl is already installed in base). > > Nick. > >
