Am 14.07.2010 um 14:25 schrieb Enrico Forestieri:
> On Wed, Jul 14, 2010 at 02:04:16PM +0200, Pavel Sanda wrote:
>> Enrico Forestieri wrote:
>>>> as i said i accept both 2 or 3 but will strongly opose to 1 since it not
>>>> only
>>>> changes the behaviour but also make impossible for anybody to reuse old
>>>> scripts
>>>> without revisiting each of them.
>>>>
>>>> since its pretty clear that you are strongly against 2 and me against 1 i
>>>> propose 3 so we can stop the flamewar.
>>>
>>> A fourth option could be using an env var, say LYX_EXPORT_OVERWRITE, with
>>> possible values {all,main,none}. This would disentangle the GUI export from
>>> the command line export.
>>
>> what would be the implicit value? if 'none', its kind of equivalent with the
>> rc patch.
>> if 'main' then i like it more, of course ;)
>
> Yes, of course none would be the default if anything other than "all" or
> "main" is specified. See the attached patch. I like this solution much more
> than 3, because it is more flexible and safer.
>
> LYX_FORCE_OVERWRITE=main lyx -e dvi foo.lyx
>
> does what you want.
Or in crontab (hypothetic example):
LYX_FORCE_OVERWRITE=main
0 6 * * * $HOME/bin/lyx-doc-update.sh
Stephan
