On Wed, Jul 13, 2011 at 3:53 PM, Richard Heck wrote:
> On 07/13/2011 05:23 AM, Rainer M Krug wrote:
> > So - could somebody guide me into the direction where I could look at
> > the code for vcs handling in LyX?
> >
> src/VCBackend.cpp
>
Thanks
Rainer
>
> rh
>
>
--
Rainer M. Krug, PhD (Con
On 07/13/2011 05:23 AM, Rainer M Krug wrote:
> So - could somebody guide me into the direction where I could look at
> the code for vcs handling in LyX?
>
src/VCBackend.cpp
rh
So - could somebody guide me into the direction where I could look at the
code for vcs handling in LyX?
Rainer
On Mon, Jul 11, 2011 at 4:52 PM, Pavel Sanda wrote:
> Rainer M Krug wrote:
> > On Mon, Jul 11, 2011 at 4:40 PM, Pavel Sanda wrote:
> > This mustn't happen - but isn't this risk higher
Rainer M Krug wrote:
> On Mon, Jul 11, 2011 at 4:40 PM, Pavel Sanda wrote:
> This mustn't happen - but isn't this risk higher when we are trying to use
> own / copied routines to check then using an established command like "git
> status"?
this is not about "using our code" vs "parsing git output
On Mon, Jul 11, 2011 at 4:40 PM, Pavel Sanda wrote:
> Rainer M Krug wrote:
> > True - but the alternative is to code the tests, which is, as discussed,
> > quite problematic.
>
> or to steal them from git.
>
But I assume that these can also change over time, especially as they are
internal.
>
Rainer M Krug wrote:
> True - but the alternative is to code the tests, which is, as discussed,
> quite problematic.
or to steal them from git.
> There is this option for git status which could be used:
> --porcelain
>Give the output in a stable, easy-to-parse format for scripts.
>
On Mon, Jul 11, 2011 at 10:01 PM, Richard Heck wrote:
> (i) "cd .." takes me to /home/rgheck/, as expected
I understand that the bash builtin cd command reinterpreting ".." to
mean slice off part of the path.
> (ii) "ls .." gives me the files in /home/rgheck/files/, as not expected.
I u
On Mon, Jul 11, 2011 at 4:22 PM, Pavel Sanda 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 ope
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.
2. there is no guarantee that the output to be parsed remain t
On Mon, Jul 11, 2011 at 4:01 PM, Richard Heck wrote:
> **
> On 07/11/2011 09:47 AM, Richard Heck wrote:
>
> On 07/11/2011 09:32 AM, Vincent van Ravesteijn wrote:
>
>
>(i) is certainly fixable, in the sense that we can spawn "git status"
> and check the return value, but it is not as easy as l
Richard Heck wrote:
> I'm a bit curious how it does this, actually. I mean: In such a way as
> properly to follow symlinks. I run into this kind of problem often.
> E.g., what ".." means seems to vary in a way I do not understand if you
> are in a symlinked directory.
thats where the fun begins. a
On 07/11/2011 09:47 AM, Richard Heck wrote:
> On 07/11/2011 09:32 AM, Vincent van Ravesteijn wrote:
>>
>>> (i) is certainly fixable, in the sense that we can spawn "git
>>> status" and check the return value, but it is not as easy as looking
>>> for .svn, say.
>>
>> We can just copy-paste the code
On Mon, Jul 11, 2011 at 3:47 PM, Richard Heck wrote:
> **
> On 07/11/2011 09:32 AM, Vincent van Ravesteijn wrote:
>
>
>(i) is certainly fixable, in the sense that we can spawn "git status"
> and check the return value, but it is not as easy as looking for .svn, say.
>
>
> We can just copy-pas
On 07/11/2011 09:32 AM, Vincent van Ravesteijn wrote:
>
>> (i) is certainly fixable, in the sense that we can spawn "git status"
>> and check the return value, but it is not as easy as looking for
>> .svn, say.
>
> We can just copy-paste the code that git uses itself to detect whether
> it is in a
On Mon, Jul 11, 2011 at 3:32 PM, Vincent van Ravesteijn wrote:
OK - so not as easy as I rememeber - well..
> (i) is certainly fixable, in the sense that we can spawn "git status" and
> check the return value, but it is not as easy as looking for .svn, say.
>
>
> We can just copy-paste the code
(i) is certainly fixable, in the sense that we can spawn "git status"
and check the return value, but it is not as easy as looking for .svn,
say.
We can just copy-paste the code that git uses itself to detect whether
it is in a repo or not ?
(ii) is definitely a different issue.
it depe
On 07/11/2011 07:52 AM, Rainer M Krug wrote:
> Hi,
>
> / /I know that git is not integrated as a vcs for LyX documents, but
> how much work would t be to include it? I remember reading somewhere
> that just a few scripts have to be changed - could somebody point me
> into the right direction?
>
> R
Hi,
* *I know that git is not integrated as a vcs for LyX documents, but how
much work would t be to include it? I remember reading somewhere that just a
few scripts have to be changed - could somebody point me into the right
direction?
Cheers,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecol
18 matches
Mail list logo
