Thread View: gnu.epoch.misc
3 messages
3 total messages
Started by Peter A Fletcher
Tue, 07 Apr 1992 23:47
Painful epoch-4.0p0 bugs
Author: Peter A Fletcher
Date: Tue, 07 Apr 1992 23:47
Date: Tue, 07 Apr 1992 23:47
55 lines
3077 bytes
3077 bytes
Hello!
Epoch 4.0 has several painful bugs in it which make using it
almost painful enough to go back to epoch-3.2. I have built epoch-4
for both the Suns and the Decstations at my site, but I only use the
Decstation version.
The first two bugs are easy to duplicate. When running as usual
in minibuffer-per-window mode (with -nm flag) with at least two epoch
screens, do the following:
- begin a command such as find-file-other-screen, leaving the prompt in the minibuffer.
- Move the mouse to another screen, and the minibuffer prompt will follow it into this screen.
- Move the mouse again back to the original screen, and click to put the cursor into it
(the prompt doesn't follow automatically, which is a small bug in itself)
- Use C-x o to return to the minibuffer
- Complete the find-file-other-screen command
The find-file-other-screen works fine, but the focusing is now
stuffed; if you move the mouse to another screen, the cursor simply
moves into the minibuffer of the previous screen. It is possible to
click in screens to move the cursor to them, but the only way to
return to a reasonable state of affairs is by killing epoch and
starting again. This combination of circumstances may sound extremely
rare, but it happens to me about once a day, even when I'm trying to
remember not to cause it.
A still nastier bug lies in store if you have lots of windows open
and decide to soldier on; eventually in unpredictable circumstances
(quitting a file and closing a screen is one example), epoch will
start to ring the bell continuously, making it near impossible to kill
on the Decstation because X comes to almost a complete halt.
A completely unrelated bug also makes life hard. I'm the only
person using my workstation, so I leave it logged in all the time with
epoch running. I usually have four epochs running at once for various
reasons, and when I come in in the morning there is usually one that
has locked up; refreshing works, the cursor fills and empties when the
mouse enters and leaves the window, but everything else is frozen; the
time is stuck on 2:15 am, none of the keys work, the mouse does not
click.
Sorry I can't be more specific about where epoch dies, because
gdb won't let me attach on a Decstation.
-peter.
--
Peter Fletcher, Internet : peterf@csis.dit.csiro.au
PhD Student Physical : CSIRO Division of Information Technology,
Phone : +61-6-2750914 ANU, Acton, Canberra ACT AUSTRALIA
-------------------------------------------------------------------------------
Re: Painful epoch-4.0p0 bugs
Author: Dev Joneja
Date: Wed, 08 Apr 1992 13:10
Date: Wed, 08 Apr 1992 13:10
5 lines
665 bytes
665 bytes
I agree about the bell-ringing bug. Under similar circumstances (dismissing a window) I have had the same problem, bringing OpenWindows to its knees on my Sun SPARC-IPC running epoch-4.0p0, SunOS 4.1.1. -Dev.
A not very painful epoch-4.0p0 bugs
Author: & Inder
Date: Thu, 09 Apr 1992 10:29
Date: Thu, 09 Apr 1992 10:29
20 lines
1237 bytes
1237 bytes
I presume that everyone knows about the following epoch bug:
With more than one screen open, close a paren then move the mouse to
another screen. The close paren makes emacs jump the cursor to
the corresponding open paren. Moving the mouse then changes the
"active" screen, so that when emacs finishes waiting and
jumps the cursor back to the closing paren, it does so in the
wrong screen, which has the effect of making the new "active"
screen change to show the point in the buffer where the paren
was inserted.
Is there a fix?
Robert.
--
---------------------------------------------------------------------------
Robert Inder, Human Communications Research Centre, University of Edinburgh
2, Buccleuch Place, Edinburgh, Scotland +44 31 650 4449
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads