Groups | Search | Server Info | Login | Register


Groups > comp.windows.x > #609

Re: xbattle 4.0 (portability) fixes

From Eli the Bearded <*@eli.users.panix.com>
Newsgroups comp.windows.x
Subject Re: xbattle 4.0 (portability) fixes
Date 2026-02-12 23:57 +0000
Organization Some absurd concept
Message-ID <eli$2602121857@qaz.wtf> (permalink)
References <qZVISAjhMUt39DyW@violet.siamics.net> <10mj1hs$109s6$6@dont-email.me> <eli$2602120117@qaz.wtf> <10ml8li$1n020$6@dont-email.me>

Show all headers | View raw


In comp.windows.x, Lawrence DOliveiro <ldo@nz.invalid> wrote:
> "Publicized" or not, it behooves a developer to at least read and
> understand the licence thay are considering using, does it not?
> After all, they were going to include a copy with their code.

The "license" is not called that. It's called "COPYING POLICIES" and
it seems to be a modified, and perhaps shortened, crib from a license
from some version of GNU Emacs. 

Oh, and I figured out how to get it run now. I had overlooked there's a
man page included. This is old-school X11 and multiplayer relies on
this one program being able to open windows on a remote system. So to
just see the game, the most basic command line would be:

    xbattle -red me

(Which is a rather plain looking grid.)

Or any x11 color:

    xbattle -$X11_COLOR_NAME me

Multiple player takes the hostname and $DISPLAY:

    xbattle -red me -blue lawrence:0.0

Then the other options are optional, but you get more of a game board.

This died with a "Memory fault":

    xbattle -red me -hex -board 100

But this gave me a complicated board:

    xbattle -red me -hex -board 20 -horizon 4 -map -localmap \
	-bases 10 -rbases 2 -armies 5 -militia 10 -hills 2 \
	-forest 3 -sea 1 -farms 2 -erode 2 -decay 2 -towns 3 \
	-guns 4 -para 4 -fight 1 -speed 1 -move 2 -digin 2

There's a noticable delay between starting the program and the board
getting drawn in the window. I could click around and things changed,
but not much, it wasn't clear what was happening. A more careful read
of the man page would probably help.

Elijah
------
wondering what other memory faults lurk in the code

Back to comp.windows.x | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

xbattle 4.0 (portability) fixes Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2026-02-11 08:37 +0000
  Re: xbattle 4.0 (portability) fixes Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-11 22:58 +0000
    Re: xbattle 4.0 (portability) fixes Eli the Bearded <*@eli.users.panix.com> - 2026-02-12 06:53 +0000
      Re: xbattle 4.0 (portability) fixes Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-12 19:11 +0000
        Re: xbattle 4.0 (portability) fixes Eli the Bearded <*@eli.users.panix.com> - 2026-02-12 23:57 +0000
          Re: xbattle 4.0 (portability) fixes Ivan Shmakov <ivan@siamics.netREMOVE.invalid> - 2026-02-13 21:15 +0000
          Re: xbattle 4.0 (portability) fixes Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-13 21:51 +0000

csiph-web