Project

General

Profile

Design #1352

cocoa5 (launch) script: sleep time

Added by John Abbott over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
John Abbott
Category:
enhancing/improving
Target version:
CoCoA-5.3.0
Start date:
25 Oct 2019
Due date:
% Done:

100%

Estimated time:
1.66 h
Spent time:
1.65 h

Description

The usual way to start CoCoA-5 is to run the script cocoa5.

This script runs some quick basic checks then calls the true executable (CoCoAInterpreter) with sensible args.

If any basic check fails then an error message is printed, and the script exits (with non-zero exit code).

The script currently sleeps for a short while after printing the error message, but before exiting.
How long should it sleep for? (Currently 1 sec)

Related issues

Related to CoCoA-5 - Design #1348: cocoa5 script for releasesClosed2019-10-23

History

#1 Updated by John Abbott over 4 years ago

#2 Updated by John Abbott over 4 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

A slightly previous version of the script would sleep for 1 sec, print error mesg, sleep for 1 sec, then exit.

An advantage of sleeping before printing the error message is that if CoCoA-5 is started inside emacs then the line sent to emacs appears in the buffer before the error message (and so does not clutter the error message).

A disadvantage is that one has to wait a second before seeing the error message (even if running CoCoA not inside emacs).

It is perhaps an unusual use-case, if one starts an xterm with CoCoA inside (that is xterm -e ./cocoa5) then the window closes just 1 sec after the error mesg is printed out -- this is not enough time to read the error mesg. After a few quick trials I think one needs at least 3 seconds to read the error message.

Should I change the script so that it does this: sleep 1; print err mesg; sleep 3; exit?

#3 Updated by John Abbott over 4 years ago

  • Priority changed from Normal to Low

One could argue that this is relatively unimportant for normal users (i.e. those who download CoCoA-5) since they should never encounter any problems which the script checks for. But then again, maybe someone will discover a bug in our release mechanism, and then it would be handy for us to receive useful feedback.

#4 Updated by Anna Maria Bigatti over 4 years ago

Good point! I think we should set the same timings in the installation script (for Mac it's called ConfigEmacs)

#5 Updated by Anna Maria Bigatti over 4 years ago

  • % Done changed from 10 to 20

updated accordingly the scripts in release-files/

#6 Updated by Anna Maria Bigatti over 4 years ago

Added sleep to ConfigEmacs mac and linux

#7 Updated by Anna Maria Bigatti over 4 years ago

  • Subject changed from cocoa5 (launch) script to cocoa5 (launch) script: sleep time

#8 Updated by John Abbott over 4 years ago

  • Status changed from In Progress to Resolved
  • Assignee set to John Abbott

I have just tried xterm -e ./cocoa5, and now prefer a 4 second wait after printing the message (perhaps it should be even longer than 4s?). It also prints a BEL (i.e. a ctrl-G which causes a beep sound when printed).

I'll check in next time I have CVS active.

#9 Updated by John Abbott over 4 years ago

  • % Done changed from 20 to 90
  • Estimated time set to 1.66 h

This has been working fine for about 2 months; so moving to feedback.

#10 Updated by John Abbott about 4 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF