I can provide a place for the download until the ftp on gnubg.org gets sorted.
On Wed, Aug 19, 2009 at 11:56 PM, Michael Petch wrote:
>
>
> On 19/08/09 3:45 PM, "Massimiliano Maini" wrote:
>
>> I would say that the only truly major issue is the one reported by Matt
>> from bgonline (money eval sc
On 19/08/09 3:45 PM, "Massimiliano Maini" wrote:
> I would say that the only truly major issue is the one reported by Matt
> from bgonline (money eval screwed with/without jacoby).
>
There is one other serious error that arose while you were gone. There is a
bug with optimizations and the Prun
).
But I can mail them personally if you
want. Let me know.
MaX.
- Message d'origine
> De : Michael Petch
> À : Michael Petch
> Cc : Massimiliano Maini ; "bug-gnubg@gnu.org"
>
> Envoyé le : Mercredi, 19 Août 2009, 21h55mn 59s
> Objet : Re: Re : Re
On 19/08/09 3:03 PM, "Christian Anthon" wrote:
> The warnings in the cl version are non-fatal, so they shouldn't hold
> back a new build, right?
>
Correct, they are non fatal, and works the same as the previous July windows
builds. I would prefer to see it built as is for now, and worry about
The warnings in the cl version are non-fatal, so they shouldn't hold
back a new build, right?
Christian.
On Wed, Aug 19, 2009 at 9:55 PM, Michael Petch wrote:
>
> I have had numerous inquiries as to when the Pruning/Optimization bug will
> be fixed. It's the primary driving force to see if Max ca
I have had numerous inquiries as to when the Pruning/Optimization bug will
be fixed. It's the primary driving force to see if Max can get a release
done for us (I'd love to test a build if he has one done, even if it is the
GUI).
Max do you have an executable (GUI version) I can download (Just th
On 19/08/09 1:36 PM, "Christian Anthon" wrote:
> Windows executables have a special flag set requiring the command line
> background (or not). I believe that is the motivation for doing things
> differently. Windows users are apparently not comfortable with having
> the command line window hangi
The best and easiest solution is to make a gui.rc for the gui settings.
Christian.
On Tue, Aug 18, 2009 at 2:48 PM, Massimiliano Maini wrote:
> Clicked on send way too fast sorry.
>
> I get this:
>
>
> GNU Backgammon 0.90-mingw 20090817gcc44
> Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004
On Wed, Aug 19, 2009 at 9:06 PM, Michael Petch wrote:
> unknown keywords to stdout.
>
> @@ -1264,10 +1252,7 @@
> break;
>
> if( !pc->sz ) {
> - outputf( _("Unknown keyword `%s'."), pch );
> - output("\n");
> -
> - outputx();
> + outputerrf( _("Unknown keyword `%s'.\n"), pch
On 19/08/09 1:06 PM, "Michael Petch" wrote:
> in main(). If someone can experiment, what happens if it is modified to
> this:
>
> #ifdef WIN32
> fNoTTY = FALSE;
> #endif
Possibly it might have to be changed to:
in main(). If someone can experiment, what happens if it is modified to
thi
On 19/08/09 9:35 AM, "Massimiliano Maini" wrote:
> One strange thing I've found (or that I've never noticed). If you do an "help
> set"
> in the CLI, you get this:
>
> and when I start the CLI on it I see this:
>
> Unknown keyword `annotation'.
> Unknown keyword `message'..
> Unknown keywor
uot;visible" in CLI (proff by "help set")
even if they
make sense only in GUI exe.
In commands.inc some commands are in #if USE_GTK ...
Removing all the #if USE_GTK in command.inc would probably solve the warning
issue,
but not the pfact that savingfrom CLI will lose GUI settings and
I've got a feeling that these warnings were hidden in older versions, probably
something to do with changes to how messages are shown.
If you save the settings from a command line build you loose all the gui
settings... This area needs a bit of an overhaul I think, the whole needing to
save any
On 18/08/09 8:52 AM, "Massimiliano Maini" wrote:
> I don't remeber this in the past ...
>
> Much in favor of option B here.
>
It wasn't a problem with the MingW builds from the 0.15 time frame. I'll
look into it.
___
Bug-gnubg mailing list
Bug-g
On 18/08/09 8:52 AM, "Massimiliano Maini" wrote:
> I don't remeber this in the past ...
>
> Much in favor of option B here.
>
It happens on older ones as far as I can remember (At least in the past
year). The current version from 0625 that I have installed does the same (I
just tried it), it
I don't remeber this in the past ...
Much in favor of option B here.
MaX.
- Message d'origine
> De : Michael Petch
> À : Massimiliano Maini ; "bug-gnubg@gnu.org"
>
> Envoyé le : Mardi, 18 Août 2009, 16h31mn 58s
> Objet : Re: [Bug-gnubg] Tr : No-g
On 18/08/09 6:48 AM, "Massimiliano Maini" wrote:
> Clicked on send way too fast sorry.
>
> I get this:
>
[snip]
Same issue as the limit command but for a different reason A9nd this issue
aAFAIK has been around for ages). If you run the GUI version gnubgautorc all
the GUI features are not
Clicked on send way too fast sorry.
I get this:
GNU Backgammon 0.90-mingw 20090817gcc44
Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 by Gary Wong.
Copyright (C) 2009 by Gary Wong and the AUTHORS; for details type `show version'
.
This program comes with ABSOLUTELY NO WARRANTY; for detai
18 matches
Mail list logo
