To save you from leaving exaEdit involuntarily, exaEdit checks whether there are some workfiles left, which have been changed but not saved yet, before the program stops the session. If there is only one workfile in your exaEdit session (that will be the MAIN), exaEdit writes the following message in the window:
Changes not saved
Press J or Y to stop:
In line mode, the second line reads as follows
Enter J or Y to stop:
Workfiles not saved: ...
- where the three dots will be replaced by the names of the workfiles which have been changed but not saved.
If you think you will do without saving your workfile(s), you only have to hit one of the keys J (for `ja') or Y (for `yes') - and exaEdit immediately finishes the session. Please note that you do not need to press the return key; one of the keys J or Y is sufficient. Of course, you do not have to use the capital letters J or Y, the single keys are enough.
Contrastingly, if you want to save your workfile(s) instead or do not want to quit exaEdit straight away, you only have to hit any other key instead of J or Y. As a result of this, the leaving process is aborted and you find yourself in the normal exaEdit session, as usual.
You should also note that a workfile is even regarded as changed if you have done as little change as replacing a character by itself.
In very rare cases, and probably only in Unix systems, exaEdit may write a message in the window after the exaEdit session has been finished:
exaEdit: Escape sequences instead of keys:
The facts of the matter are these:
The information that one of the special keys, e.g.
right arrow, has been pressed, sometimes reaches a
certain stage in the operating system in the form of a sequence
of other keys. So, it may occur, for example, that the
right arrow key is translated into the sequence of the
three keys Esc[C
. If they reach the operating system
with very short intervals, the operating system manages to
translate them into the information right arrow key.
If the time intervals between the individual keys of the sequence
are too long - as it may occur in case of highly charged lines
between terminal and computer - the keys are passed on as separate
keys, which are useless for exaEdit in this form. This is the
reason why exaEdit has a mechanism to complete the single
characters to the correct sequence right arrow key.
All the instances where this mechanism is used are counted and the number of
these events is displayed in the window after the actual exaEdit
session has been finished.
If the displayed number is small, you may ignore the message. But if there appear larger numbers after the end of your session, there might be some problem. exaEdit completes any recognized sequence correctly but there might have been some cases that exaEdit did not recognize.