Re: Sangband spontaneous exits

On Jul 27, 2:48 pm, Phil Cartwright <pca...@xxxxxxxxxxxxxxxx> wrote:
I have observed a pattern: they occur when the document-reader
subroutine runs. The thing with press space to continue, arrows to move
etc. that displays help, self-knowledge, message recall, and a lot of
other stuff.

If the session is fairly old, opening one of these and then leaving it
idle causes it to spontaneously exit the program after around 10-15
seconds of idling. Which is very strange since it should simply be
waiting for user input.

If the session is new it seems to be immune.

It's probably the loop that waits for a key at the reader's prompt
that's the culprit. I can't imagine anything else being active under the
circumstances where it keeps happening. Why it eventually interprets no
key being pressed for a while as an exit-without-save command is a
doggone mystery though. It isn't even actually crashing -- no illegal
operation message. It is just deciding on its own to quit more-or-less
normally, except for not saving on the way out.

--
There's only four things you can be certain of: taxes, change, spam, and
death.

Just to note, I have never observed this "spontaneous clean exit"
since installing 1.0 - I've had a couple of crashes, but they've both
given me the "sangband.exe has encountered a problem and needs to
close" message. FWIW, they were both related to the quiver.

There is an issue with the -more- prompt though (or the "(+)" as it is
in S). I almost always have to press one extra key *after* the last
(+) is gone. So it *seems* that the prompts are all clear and the game
is waiting for my input, but actually the first key I press is ignored
(as if it's clearing one more (+)), and only then can I continue
playing. I've got used to this now, but it plays havoc with macros. I
wonder if it is related to the phenomenon Phil describes.

CC

.

Relevant Pages

  • Re: testing whether a process has completed..
    ... NOW - I NEED TO KNOW HOW TO CHECK IF THE RUBY PROGRAM IS WAITING FOR INPUT ... So your saying that, when running a program from the command prompt, it ... that is the time consuming part of writing Expect scripts. ...
    (comp.lang.ruby)
  • Re: ModelSim control
    ... Getting user input from VHDL is easy enough, ... Getting user input from Tcl is probably even easier, ... -- first prompt is polite ...
    (comp.lang.vhdl)
  • Re: Interactive scripts, /dev/tty and standard error
    ... > Say I need to write a script that requires user input. ... > prompt go to standard error? ... Consider if you want to force the script to be "non-batchable" If you ... You can always force a user response to come from a terminal, overriding STDIN ...
    (comp.unix.shell)
  • Re: testing whether a process has completed..
    ... NOW - I NEED TO KNOW HOW TO CHECK IF THE RUBY PROGRAM IS WAITING FOR INPUT ... Because you have done "ruby my_program.rb", that's in a shell running ... So your saying that, when running a program from the command prompt, it ...
    (comp.lang.ruby)
  • Re: Puzzle!
    ... If the user types nothing but a carriage return, ... or repeating the prompt or anything. ... The scanf() call is still ... running, waiting for more input, since "%d" skips leading white ...
    (comp.lang.c)