wjc@ho5cad.ATT.COM (02/29/88)
In article <110@ureka.UUCP> charlie@ureka.UUCP (charlie crassi) writes: > Everything works OK except you never know where the cursor is. The > only cure I've found is to log out and back in again, then everything > is back to normal. > > Question: > > Has anybody seen this on their machine ? Do you have a fix you can > e-mail to me, Please ? > I don't use the calendar, so I don't know for sure what is happening to you. My guess, though, is that it turns off the cursor intenionally (pretty normal for a graphical interface) and then just neglects to turn it back on. If that's the case, you can do it yourself far easier than logging out. Try this from the shell level: $ echo '\033[=0C\c' # cursor on $ echo '\033[=1C\c' # cursor off Cursor visibility is a per-window attribute.
gberg@hpindda.HP.COM (Greg Berg) (03/01/88)
/ charlie@ureka.UUCP (charlie crassi) / 5:22 pm Feb 26, 1988 / > Pcal problems, need help ! > > Has anybody else had the same problem running Pcal on the 3B1 ? > When Calendar is running from the user agent it performs acceptably > and exits as it should. When Pcal is run from the shell it runs > acceptably but upon exit from Pcal, there is no longer a cursor. > > Everything works OK except you never know where the cursor is. The > only cure I've found is to log out and back in again, then everything > is back to normal. > ---------- Blame it on the user agent. From my experiences the cursor does not disappear when pcal exits; the cursor is in a small window in the left upper corner (amid garbage). Next time you run pcal from the [kc]sh hit return a few times- you should be able to find it. Logging out is the easiest way to clean up after running pcal from a shell.