On 18/08/09 6:48 AM, "Massimiliano Maini" <[email protected]> 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 understood. If you do save settings from the CLI and reload the CLI it will be fine (All the misunderstood command should not be saved), however all the GUI settings will be lost, and will be defaulted when you next run the GUI version. Its not anything new from my experience with windows builds in the past. On *nix you can run with the -t option with a GUI version and get the CLI. Since the GUI variant is running in CLI mode it knows all about the GUI commands so doesn't throw errors, and ignored hat it doesn't need. I see a few options. A) Modify GnuBG so that the RC file can be overridden at the command line and allow the CLI and the GUI to run with different file B) Modify GnuBG's CLI build to include all the command entries for GUI options and quietly ignore what is not needed when CLI is launched, and Save Settings would still save out the data associated with commands that are ignored. C) Leave things status quo and people can just ignore the errors. Option C is least work and probably fine for now, and the issue isn't new. Option B is probably the best solution but most work. Option A is relatively easy to implement but users may come to expect the GUI and CLI versions installed on their system will share settings. Michael _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
