On Mon, Jul 11, 2011 at 4:22 PM, Pavel Sanda <sa...@lyx.org> wrote:
> Rainer M Krug wrote:
> > I might be missing something basic, but are there any problems with using
> >
> > git status FILE_OF_LYX_FILE
> >
> > and to parse the output?
>
> 1. it feels wrong to spawn new external command for each file/child opened.
>
True - but the alternative is to code the tests, which is, as discussed,
quite problematic.
2. there is no guarantee that the output to be parsed remain the same
> accross
> git versions.
>
There is this option for git status which could be used:
--porcelain
Give the output in a stable, easy-to-parse format for scripts.
Currently this is identical to --short output, but is guaranteed
not to change in the future, making it safe for scripts.
> 3. possible network problems written in other mail.
>
But if "git status" does not work, I do not expect the other "git" commands
to work?
Rainer
>
> pavel
>
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax (F): +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
