Branko Čibej wrote on Wed, 07 Feb 2018 14:21 +0100:
> No; because 'svn diff' hides differences in end-of-line style and
> keyword expansions, it has to preprocess the files in the working copy,
> and it sends those preprocessed files to the external diff wrapper.
>
> We could theoretically skip th
On 07.02.2018 15:06, Nico Kadel-Garcia wrote:
> On Wed, Feb 7, 2018 at 8:21 AM, Branko Čibej wrote:
>
>> No; because 'svn diff' hides differences in end-of-line style and
>> keyword expansions, it has to preprocess the files in the working copy,
>> and it sends those preprocessed files to the exte
On Wed, Feb 7, 2018 at 8:21 AM, Branko Čibej wrote:
> No; because 'svn diff' hides differences in end-of-line style and
> keyword expansions, it has to preprocess the files in the working copy,
> and it sends those preprocessed files to the external diff wrapper.
>
> We could theoretically skip t
On 07.02.2018 13:07, Juraj Priskin wrote:
> Hi,
>
> I'm using vimdiff as my diff tool for svn diff. The wrapper is simple
> one line command "vimdiff -R $6 $7". Having open vimdiff, it happens
> often that I would like to fix my local changes, mostly typos, small
> stuff, etc. It would be thus h
Hi,
I'm using vimdiff as my diff tool for svn diff. The wrapper is simple one line
command "vimdiff -R $6 $7". Having open vimdiff, it happens often that I would
like to fix my local changes, mostly typos, small stuff, etc. It would be thus
handy if I can do it in vimdiff, rather than open th
