On 03/09/2012 03:20 PM, Stephan Witt wrote:
Am 09.03.2012 um 20:18 schrieb Richard Heck:
On 03/09/2012 11:06 AM, Stephan Witt wrote:
Ok, here comes the patch. If anybody can give it a try - especially on Windows
- I'm interested in the result. Otherwise I'll commit it on Sunday or so...
I've
Am 09.03.2012 um 20:18 schrieb Richard Heck:
> On 03/09/2012 11:06 AM, Stephan Witt wrote:
>>
>> Ok, here comes the patch. If anybody can give it a try - especially on
>> Windows - I'm interested in the result. Otherwise I'll commit it on Sunday
>> or so... I've introduced the FileName::parentP
On 03/09/2012 11:06 AM, Stephan Witt wrote:
Ok, here comes the patch. If anybody can give it a try - especially on
Windows - I'm interested in the result. Otherwise I'll commit it on
Sunday or so... I've introduced the FileName::parentPath() method to
avoid the infinite loop when FileName::on
Am 07.03.2012 um 19:16 schrieb Richard Heck:
> On 03/07/2012 09:32 AM, Stephan Witt wrote:
>> Am 07.03.2012 um 15:15 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
I don't like hard-coding the knowledge how subversion developers organize
their meta-data.
>>> More thoughts - what about
Am 08.03.2012 um 11:41 schrieb Abdelrazak Younes:
> On Wed, Mar 7, 2012 at 3:15 PM, Pavel Sanda wrote:
>> Stephan Witt wrote:
>>> I don't like hard-coding the knowledge how subversion developers organize
>>> their meta-data.
>>
>> More thoughts - what about this proposal:
>> 1. We completely ki
On Wed, Mar 7, 2012 at 3:15 PM, Pavel Sanda wrote:
> Stephan Witt wrote:
>> I don't like hard-coding the knowledge how subversion developers organize
>> their meta-data.
>
> More thoughts - what about this proposal:
> 1. We completely kill parsing of 1.6 metadata in .svn.
> 2. If possible than wr
Stephan Witt wrote:
> 1. and 2. (minus --xml) is essentially my already existing patch.
> 3. is a thing I can live with
>
> Now we're all happy, aren't we? :)
Yes, thanks :)
Pavel
On 03/07/2012 09:32 AM, Stephan Witt wrote:
Am 07.03.2012 um 15:15 schrieb Pavel Sanda:
Stephan Witt wrote:
I don't like hard-coding the knowledge how subversion developers organize their
meta-data.
More thoughts - what about this proposal:
1. We completely kill parsing of 1.6 metadata in .s
Am 07.03.2012 um 15:15 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> I don't like hard-coding the knowledge how subversion developers organize
>> their meta-data.
>
> More thoughts - what about this proposal:
> 1. We completely kill parsing of 1.6 metadata in .svn.
> 2. If possible than write co
Stephan Witt wrote:
> I don't like hard-coding the knowledge how subversion developers organize
> their meta-data.
More thoughts - what about this proposal:
1. We completely kill parsing of 1.6 metadata in .svn.
2. If possible than write common routine for both 1.6/1.7 (I assume the output
of "s
Stephan Witt wrote:
> > It would work but it implies external svn call(s) for each opened files no
> > matter whether the file
> > is under the control :-/ I'm not much happy, but you are the boss now...
>
> I don't like hard-coding the knowledge how subversion developers organize
> their meta-d
Am 05.03.2012 um 14:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> Stephan, do you still have some time to look on this? I mean
>>> a) some routine to check existence of parental .svn for 1.7 SVN
>>> b) in case a) succeeds external svn call to check file being under SVN
>>> control
>>> (a&b p
Stephan Witt wrote:
> > Stephan, do you still have some time to look on this? I mean
> > a) some routine to check existence of parental .svn for 1.7 SVN
> > b) in case a) succeeds external svn call to check file being under SVN
> > control
> > (a&b perhaps just as fallback to current current che
Am 03.03.2012 um 20:36 schrieb Pavel Sanda:
> Lars Gullik Bj?nnes wrote:
>
>> Stephan Witt wrote:
>>> second bad news is that i'm short of time these weeks to debug it :)
>>
>> Do you know more about the details? Perhaps I can do something about that.
>
> Stephan, do you still have some time to
Vincent van Ravesteijn wrote:
> Well, why don't you look in the git source. They will have found a robust
> way to do this.
Of course linking to their library would be best.
one day :)
Pavel
In case a) is written in general way (bool checkparentdirs(".svn"))
the doors for basic git support in LyX are opened (I guess one weekend
coding& debugging).
Well, why don't you look in the git source. They will have found a robust way
to do this.
Vincent
Lars Gullik Bj?nnes wrote:
> >> Le 26/10/2011 14:37, Pavel Sanda a écrit :
> >>> i have painful experience with applications which scan neighbourhood
> >>> of the folders you are working in case you are working in networked
> >>> filesystem. one mount point freezes and unrelated application freezes
Pavel Sanda writes:
| Jean-Marc Lasgouttes wrote:
>> Le 26/10/2011 15:01, Pavel Sanda a écrit :
>>> the whole problem arised because "just checking" .svn dir in the current
>>> folder
>>> is no more possible with subversion 1.7.
>>
>> Because only the top svn directory has information, right?
>
Pavel Sanda writes:
| Jean-Marc Lasgouttes wrote:
>> Le 26/10/2011 14:37, Pavel Sanda a écrit :
>>> i have painful experience with applications which scan neighbourhood
>>> of the folders you are working in case you are working in networked
>>> filesystem. one mount point freezes and unrelated ap
Georg Baum writes:
| Pavel Sanda wrote:
>
>> it just feels wrong. when document has 10 childern we will execute it 10
>> times. when we introduce git then 20 times? if some win user has firewall
>> will we ask about execution of svn/git binary upon opening lyx manual for
>> the first time after l
On 26/10/2011 21:56, Georg Baum wrote:
Pavel Sanda wrote:
it just feels wrong. when document has 10 childern we will execute it 10
times. when we introduce git then 20 times? if some win user has firewall
will we ask about execution of svn/git binary upon opening lyx manual for
the first time a
Georg Baum wrote:
> Parsing internal svn files from LyX looks as wrong to me as starting the svn
> client a dozen times. A better solution would be to use svn not as a binary,
> but link to the library. I even tried that some time ago. It does not look
> too bad, but I never finished it.
yep, t
Pavel Sanda wrote:
> it just feels wrong. when document has 10 childern we will execute it 10
> times. when we introduce git then 20 times? if some win user has firewall
> will we ask about execution of svn/git binary upon opening lyx manual for
> the first time after lyx is launched and so on...
Am 26.10.2011 um 15:01 schrieb Pavel Sanda:
> Jean-Marc Lasgouttes wrote:
>> Le 26/10/2011 14:37, Pavel Sanda a écrit :
>>> i have painful experience with applications which scan neighbourhood
>>> of the folders you are working in case you are working in networked
>>> filesystem. one mount point f
Am 26.10.2011 um 16:21 schrieb Enrico Forestieri:
> On Wed, Oct 26, 2011 at 04:02:08PM +0200, Pavel Sanda wrote:
>> Vincent van Ravesteijn wrote:
>>> So I'm happy they finally saw the light.
>>
>> :) if one seeks the light he should probably switch to git...
>>
>> breaking older things to work m
On Wed, Oct 26, 2011 at 04:02:08PM +0200, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > So I'm happy they finally saw the light.
>
> :) if one seeks the light he should probably switch to git...
>
> breaking older things to work means perhaps one reason less
> to continue to use svn at a
Vincent van Ravesteijn wrote:
> So I'm happy they finally saw the light.
:) if one seeks the light he should probably switch to git...
breaking older things to work means perhaps one reason less
to continue to use svn at all.
p
Op 26-10-2011 15:45, Pavel Sanda schreef:
Jean-Marc Lasgouttes wrote:
Le 26/10/2011 15:01, Pavel Sanda a écrit :
the whole problem arised because "just checking" .svn dir in the current
folder
is no more possible with subversion 1.7.
Because only the top svn directory has information, right?
Jean-Marc Lasgouttes wrote:
> Le 26/10/2011 15:01, Pavel Sanda a écrit :
>> the whole problem arised because "just checking" .svn dir in the current
>> folder
>> is no more possible with subversion 1.7.
>
> Because only the top svn directory has information, right?
yes. dont know the motivations
Le 26/10/2011 15:01, Pavel Sanda a écrit :
the whole problem arised because "just checking" .svn dir in the current folder
is no more possible with subversion 1.7.
Because only the top svn directory has information, right?
JMarc
Jean-Marc Lasgouttes wrote:
> Le 26/10/2011 14:37, Pavel Sanda a écrit :
>> i have painful experience with applications which scan neighbourhood
>> of the folders you are working in case you are working in networked
>> filesystem. one mount point freezes and unrelated application freezes
>> as well
Op 26-10-2011 14:52, Jean-Marc Lasgouttes schreef:
Le 26/10/2011 14:37, Pavel Sanda a écrit :
i have painful experience with applications which scan neighbourhood
of the folders you are working in case you are working in networked
filesystem. one mount point freezes and unrelated application fre
Le 26/10/2011 14:37, Pavel Sanda a écrit :
i have painful experience with applications which scan neighbourhood
of the folders you are working in case you are working in networked
filesystem. one mount point freezes and unrelated application freezes
as well.
considering that svn is used by small
Vincent van Ravesteijn wrote:
> Against all, unless you convince me this that this option really can't be
> enabled always. I'm afraid this will become just another option that should
> be there out of principle, but isn't ever used by the user.
>
>>> there is absolutely no reason to disable it f
Op 26-10-2011 13:41, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Stephan
I'm in favor of having some better settings for the version control
system(s), but I don't like to have another option whether to use VCS or
not.
you are against general "use vcs" or against "subversion support", "
Vincent van Ravesteijn wrote:
>> Stephan
> I'm in favor of having some better settings for the version control
> system(s), but I don't like to have another option whether to use VCS or
> not.
you are against general "use vcs" or against "subversion support", "git support"
checkboxes?
> there i
Op 26-10-2011 13:03, Stephan Witt schreef:
Am 26.10.2011 um 12:05 schrieb Pavel Sanda:
Stephan Witt wrote:
Pavel, I've tested this patch with 1.7 SVN and on Linux with 1.6.
Because I've only the LYX SVN repository at hand I don't want to test
all operations. But the detection of SVN repository
Am 26.10.2011 um 12:05 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>> Pavel, I've tested this patch with 1.7 SVN and on Linux with 1.6.
>>> Because I've only the LYX SVN repository at hand I don't want to test
>>> all operations. But the detection of SVN repository members is working now.
>>
>> I
Jean-Marc Lasgouttes wrote:
> Can't we just read the local files? I agree that network access when
> opening a file is wrong.
i believe svn will only access local files (though i didn't test).
pavel
Le 26/10/2011 12:21, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 26/10/2011 12:05, Pavel Sanda a écrit :
i feel uneasy about this stuff being executed for opening each lyx file
(the same problem as with git), directory traversal is not better.
shall we introduce some gui variable like
Jean-Marc Lasgouttes wrote:
> Le 26/10/2011 12:05, Pavel Sanda a écrit :
>> i feel uneasy about this stuff being executed for opening each lyx file
>> (the same problem as with git), directory traversal is not better.
>> shall we introduce some gui variable like "Use revision control systems"
>> or
Le 26/10/2011 12:05, Pavel Sanda a écrit :
i feel uneasy about this stuff being executed for opening each lyx file
(the same problem as with git), directory traversal is not better.
shall we introduce some gui variable like "Use revision control systems"
or am i oversensitive?
Is it a matter of
Stephan Witt wrote:
> > Pavel, I've tested this patch with 1.7 SVN and on Linux with 1.6.
> > Because I've only the LYX SVN repository at hand I don't want to test
> > all operations. But the detection of SVN repository members is working now.
>
> I missed some status flag: "I" stands for ignore.
Hi all :
The folder.svn in version 1.7 has two subfolders pristine and tmp, while
the.svnversion 1.6, I remember several subfolders, such
as propdel, propset and three more that are handled
by LyX. When accessing LyX to the version 1.7 is all completelychanged.
Regards
Miguel
Am 24.10.2011 um 17:11 schrieb Buenas Noticias:
> I don't know make these. I am a normal user, what discover a problem in
> the svn version control.
>
You're able to upgrade your SVN to 1.7 and cannot create a ticket in our
trac-system?
Did you try it already?
Stephan
> El 24/10/11 17:05, Ste
I don't know make these. I am a normal user, what discover a problem in
the svn version control.
Regards
El 24/10/11 17:05, Stephan Witt escribió:
> Am 24.10.2011 um 16:55 schrieb Buenas Noticias:
>
>> Hi all :
>>
>> I used a repository, made with svn 1.6 and I open my LyX documents, and they
>
Am 24.10.2011 um 16:55 schrieb Buenas Noticias:
> Hi all :
>
> I used a repository, made with svn 1.6 and I open my LyX documents, and they
> worked perfectly. Then I did a svn upgrade to version 1.7 and LyX, you can
> not put them under version control, so I conclude that there is a problem
>
Hi all :
I used a repository, made with svn 1.6 and I open my LyX documents, and
they worked perfectly. Then I did a svn upgrade to version 1.7 and LyX,
you can not put them under version control, so I conclude that there is
a problem with this newversion and the program LyX 2.1.0svn.
Regards
Am 23.10.2011 um 14:15 schrieb Stephan Witt:
> Am 21.10.2011 um 22:25 schrieb Stephan Witt:
>
>> Am 21.10.2011 um 21:38 schrieb Lars Gullik Bjønnes:
>>
>>> Stephan Witt writes:
>>>
>>> | Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
> Buenas Noticias wrote:
>> Ok. Subversion 1.7 is
Am 21.10.2011 um 22:25 schrieb Stephan Witt:
> Am 21.10.2011 um 21:38 schrieb Lars Gullik Bjønnes:
>
>> Stephan Witt writes:
>>
>> | Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
>>>
Buenas Noticias wrote:
> Ok. Subversion 1.7 is incompatible with LyX.
maybe i was wrong and p
Am 21.10.2011 um 23:30 schrieb Lars Gullik Bjønnes:
> Stephan Witt writes:
>
> | Am 21.10.2011 um 21:38 schrieb Lars Gullik Bjønnes:
>>
>>> Stephan Witt writes:
>>>
>>> | Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
> Buenas Noticias wrote:
>> Ok. Subversion 1.7 is incompatible w
Stephan Witt writes:
| Am 21.10.2011 um 21:38 schrieb Lars Gullik Bjønnes:
>
>> Stephan Witt writes:
>>
>> | Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
>>>
Buenas Noticias wrote:
> Ok. Subversion 1.7 is incompatible with LyX.
maybe i was wrong and problem is not with lyx p
Am 21.10.2011 um 21:38 schrieb Lars Gullik Bjønnes:
> Stephan Witt writes:
>
> | Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
>>
>>> Buenas Noticias wrote:
Ok. Subversion 1.7 is incompatible with LyX.
>>>
>>> maybe i was wrong and problem is not with lyx per se.
>>> can you please try agai
Stephan Witt writes:
| Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
>
>> Buenas Noticias wrote:
>>> Ok. Subversion 1.7 is incompatible with LyX.
>>
>> maybe i was wrong and problem is not with lyx per se.
>> can you please try again with completely new repo (checkout from 1.7)
>> or upgrade as st
Am 21.10.2011 um 20:21 schrieb Stephan Witt:
> Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
>
>> Buenas Noticias wrote:
>>> Ok. Subversion 1.7 is incompatible with LyX.
>>
>> maybe i was wrong and problem is not with lyx per se.
>> can you please try again with completely new repo (checkout from
Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
> Buenas Noticias wrote:
>> Ok. Subversion 1.7 is incompatible with LyX.
>
> maybe i was wrong and problem is not with lyx per se.
> can you please try again with completely new repo (checkout from 1.7)
> or upgrade as stated by Enrico?
It's LyX having
Am 21.10.2011 um 14:09 schrieb Pavel Sanda:
> Buenas Noticias wrote:
>> Ok. Subversion 1.7 is incompatible with LyX.
>
> maybe i was wrong and problem is not with lyx per se.
> can you please try again with completely new repo (checkout from 1.7)
> or upgrade as stated by Enrico?
>
> pavel
One
Hi Pavel :
I made a test document, and all commands to get a working copy. In the
beginning everything is fine, but the icons are not activatedin LyXand I
can not use the svn version control.
Miguel
El 21/10/11 14:09, Pavel Sanda escribió:
> Buenas Noticias wrote:
>> Ok. Subversion 1.7 is incomp
Buenas Noticias wrote:
> Ok. Subversion 1.7 is incompatible with LyX.
maybe i was wrong and problem is not with lyx per se.
can you please try again with completely new repo (checkout from 1.7)
or upgrade as stated by Enrico?
pavel
On Fri, Oct 21, 2011 at 10:38:51AM +0200, Buenas Noticias wrote:
> Ok. Subversion 1.7 is incompatible with LyX. Subversion 1.6 work fine.
> Now I can not put my documents under version control with the 1.7, so
> if I could do with the 1.6 version.
This is not true. Please, read
http://subversion
On Fri, Oct 21, 2011 at 09:09:00AM +0200, Pavel Sanda wrote:
> Stephan Witt wrote:
> > Do you know more about the details? Perhaps I can do something about that.
>
> no, first time i hear about that. one needs to install svn 1.7 and see whats
> going on...
Subversion 1.7 does not automatically u
Ok. Subversion 1.7 is incompatible with LyX. Subversion 1.6 work fine.
Now I can not put my documents under version control with the 1.7, so
if I could do with the 1.6 version.
Regards
Miguel
El 21/10/11 08:40, Pavel Sanda escribió:
> Buenas Noticias wrote:
>> Hi all :
>>
>> I am using LyX 2.1.0
Stephan Witt wrote:
> Do you know more about the details? Perhaps I can do something about that.
no, first time i hear about that. one needs to install svn 1.7 and see whats
going on...
pavel
Am 21.10.2011 um 08:44 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Perhaps it's the same with Mandriva 1.7?
>
> i think he speaks about svn versions.
O yes, that's more probably.
>> I am using LyX 2.1.0svn and treatment versions with svn. So far
>> everything has worked fine, but when Mandriv
Stephan Witt wrote:
> Perhaps it's the same with Mandriva 1.7?
i think he speaks about svn versions.
pavel
Buenas Noticias wrote:
> Hi all :
>
> I am using LyX 2.1.0svn and treatment versions with svn. So far
> everything has worked fine, but when Mandriva upgrade subversion to
> 1.7.0, it stopped working. The LyX Tutorial says that svn was tested
> with versions 1.4 and 1.6 working well. Any idea to w
Am 21.10.2011 um 08:17 schrieb Buenas Noticias:
> Hi all :
>
> I am using LyX 2.1.0svn and treatment versions with svn. So far
> everything has worked fine, but when Mandriva upgrade subversion to
> 1.7.0, it stopped working. The LyX Tutorial says that svn was tested
> with versions 1.4 and 1.6 w
Hi all :
I am using LyX 2.1.0svn and treatment versions with svn. So far
everything has worked fine, but when Mandriva upgrade subversion to
1.7.0, it stopped working. The LyX Tutorial says that svn was tested
with versions 1.4 and 1.6 working well. Any idea to work with 1.7.0?.
I can not go back
68 matches
Mail list logo
