Re: Diff Project --invoke-diff-cmd part
From: Gabriela Gibson <gabriela.gibson_at_gmail.com>
Date: Tue, 23 Apr 2013 11:33:46 +0100
Many thanks for the inspiring feedback!
Gabriela
--------------------------------------------
Julian Foad wrote:
>> * This patch breaks the override --internal-diff for now, because
> OK, we'll have to decide what should override what. I have not formed
Personally I feel that if you define an option on the command line, it
Also, I think the --internal-diff-or-merge should turn off whatever
Paul Watson mentioned on the user list:
that he would like to use mime-types to define what diff program to
Should the config file store pair values, mime-type and the
New command line design example:
invoke-diff-cmd="---MIME-TYPE=custom_mime_type diffProg ---f1 ....
or, if you just want the diff program you select to be applied to any
invoke-diff-cmd="diff ---f1 ..."
The corresponding config file entries would look like:
INVOKE_DIFF_MIME_TYPE_1=myCustomDiffType
INVOKE_DIFF_MIME_TYPE_2=default
I wasn't sure if this kind of dev talk belongs on the user list, so I
> I think it would be desirable to be able to create arguments
Just to clarify, would you like "+---f1" expanding to
-----------------------------------------
> Yes. Also, please document the return value (NULL-terminated argv
I thought for quite a while that apr_array_header_t should be used
Question 1: does/should svn_io_create_custom_diff_cmd live in the API,
Question 2: Given the additional issue of the diff_cmd_baton data
-----------------------------------------
> I like the idea! I note that you don't draw attention to any existing
> http://subversion.tigris.org/issues/show_bug.cgi?id=2044
Yes, the new command fixes this.
> Also, a minor design nit (sorry, no code review): The "---f1"
That's why I picked it --- I checked extensively, and no-one uses a
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.