[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

AW: [TSVN] Feature: Diff-Scripts

From: Martin Eckardt <Martin.Eckardt_at_micronova.de>
Date: 2005-07-15 09:41:07 CEST

> So you mean instead of just using the file extension to
> figure out which diff tool to use we should also take the
> mime type into account?
Yes, that would be great.
Should we only use the svn:mime-type property determining the type or are
there other methods?

> Good idea, question is though how to handle this:
> - what has higher priority: extension or mime type (I guess
> it would be mime type here?)
I thought about it again. Mime type should be first priority IMO
Because it gives you finer control. One file ext could have multiple
mimetypes and one mime type could have multiple file extensions.

> - What should the dialog look like where this can be configured?
> Maybe an additional column like this:
> ext mimetype path
> .xml application/msword vbscript
> .xml TortoiseMerge
> Or even better, if a mimetype is set, then it *only* is
> used if the file to diff has that mimetype - for files
> without the mimetype the default diff viewer is used.

That would be better, so something like this could be used:

   ext mimetype path
   * application/msword vbscript

That one would have another advantage, you don't have to set .xml to Tmerge.

Because if no mime-type is set Tmerge is used automatically.

And if mimetype is empty the ext could be used.
Would this need to many time to read the property? I don't know such things.

I have to try it...
> Of course, a patch would be great!
I'm two weeks away in croatia. Could you file an issue and assign it to me.
That would be great.
I had set up an complete build environment at home.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jul 15 09:42:07 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.