Re: [gnugo-devel] Fwd: gnugo: stepping thru a saved game in ascii mode is difficult without () around current move

[bump]

Paul wrote:

> I see and understand you reasons for using ASCII.  In this case, you
> could also try running GNU Go from under Emacs, if you use it anyway.
> Emacs GNU Go mode has been largely improved recently.

The gnugo.el that is supplied with gnugo-3.7.2 addresses
exactly the requests that are made.

If you run it under X windows you get a graphical display
of the board with XPM's. 

However if you run emacs -nw it will run in terminal mode.
It may require emacs21. Load gnugo.el and then:

> And since I'm being such a pest, I can't be hurting my
> reputation any more to ask if it wouldn't be too much
> trouble to add some "timer reading" which tells the player
> exactly how long the program took to calculate a move (at
> whatever depth). I think coding it would be as simple as
> logging the time at the begin of the turn and subtracting
> that from the time at the end of the move, and then
> displaying the difference.

The mode line displays:

(Playing GNU Go [0 0 :8 0 :0])

Here the five numbers are

Black Captures
White Captures :
Move Number
Size of the undo stack :
Time waiting for the most recent move

The timing information is what you asked for.

> Stepping thru a loaded game in ascii mode, it gets hard to see where the
> next stone has just been put -- because unlike during live play, there
> are no brackets around the last move made.
> (X) (O)  Right?

If you load a saved game in emacs mode, the last move is
properly bracket.

Stepping through the game is now implemented in the distributed
gnugo.el. You could go back to the beginning of the game with

'<' then step through it with 'f' and 'b' to go forward or
backward through the game record.

> For that matter, that last move could be displayed somewhere on the
> screen.
> 
> And for that matter, all the moves could likely be displayed along the
> right-hand side of the screen..!

'h' will produce a list of all moves in the minibuffer.

The version of gnugo.el that I just discussed is distributed
with 3.7.2. The version of gnugo.el that is distributed with
3.6 is Thi's version 2.2.8. In that version the redo is not
implemented, sgf handling is a little broke and the mode
line is different but does include the timing info.

According to:

http://packages.debian.org/unstable/games/gnugo
http://packages.debian.org/testing/games/gnugo

The version of GNU Go you are distributing is 3.6. (Forget
about debian stable.) I recall that debian testing is
frozen now, but maybe you should put gnugo 3.7.2 into
debian unstable.

Dan