Re: [Gramps-devel] argparser.py nuance question

[Michiel N. <m.d...@he...>]

Hi,

I am tempted to rephrase the question into:

There is no call to config.save() in cli/argparser.py. Is this a 
deliberate choice or is this a bug?

Personally I am quite happy with how it works at the moment. I realize 
now, I can solve an issue I had with unittests by adding -c 
preferences.eprefix='E%04d' while I wouldn't want this preference when 
using the Gui because I have one familytree with more then 10000 events 
(so I use 'E%05d').

Michiel

On 03/10/2011 06:05 PM, Paul Franklin wrote:
> I believe you added the code to argparser.py in trunk to
> set gramps configuration variables, although I also think
> others have subsequently modified it.
>
> My question is, did you intend a user to set a configuration
> variable (via the command line), and then have gramps be
> finished? To only set that variable and then quit?  Or did
> you want it to set that configuration variable and then go
> on to start up a normal GUI gramps session?
>
> This query is motivated by a combination of two things on
> the bug tracker, and the reply to one of them:
>
> http://www.gramps-project.org/bugs/view.php?id=4733
> http://www.gramps-project.org/bugs/view.php?id=4735
>
> For instance, should I be able to say:
>
> gramps --config=behavior.check-for-updates:0
>
> and then have it start up a gramps?  Or was it your
> intent that a gramps then be started after that command,
> in a second command line, for instance after possibly
> changing other configuration variables first?
>
> Thanks.
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>