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

Re: /notempfile

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-10-03 20:03:31 CEST

Tobias Schäfer wrote:
> On Monday 25 September 2006 09:04, Gavin Lambert wrote:
>
> Let me summarize this tread:
>
> 1. The automation interface which is currently
> /command:update /path="d:\temp\wc\" /notempfile
> changes to
> /command:update /path="d:\temp\wc\"
> Since the switch /notempfile is not evaluated there won't be a change in
> behavior if it is passed. Users using the automation interface cannot
> forget /tempfile anymore.
>
> 2. The interface for the shell extension is currently
> /command:update /path="%temp%\svn1234.tmp"
>
> You propose to change it to:
> /command:update /tempfile="%temp%\svn1234.tmp"
>
> If we change the following I agree:
> - rename /tempfile to /pathfile to make it clear that /path and /pathfile
> are mutally exclusive.
> - add a switch to delete the file specified by /pathfile by tortoiseproc
> instead of always deleting it. This allows the calling application to
> delete the file after having called tortoiseproc.
>
> This is my proposal based on your ideas:
> /command:update /pathfile="%temp%\svn1234.tmp" /deletepathfile
>
> This change will break all calls which currently don't specify /notempfile.
> All calls from the shell extension will be changed to reflect this new
> interface.
>
> What should tortoiseproc do if both /path and /pathfile are given? I would
> add both path lists to a single path list internally.

Since they're mutually exclusive, I would make TortoiseProc show an
error dialog box. That way, anyone calling it the wrong way will realize
it immediately.

> Pathfile is currently a file in unicode encoding. To make it easier to pass
> a list of files we should also support simple ascii encoding. This is a
> different issue though. This is to support what you proposed with the
> parameter /listfile

simple ASCII encoding doesn't work very well. Paths in windows can have
any chars (except of course the well known exceptions like ?*...). A
path to a file like:
Âäöéàè.txt
wouldn't work with plain ASCII (especially if the filename contains
chars which are not available in the default code page).
So I would stick to UNICODE (or at least UTF8) format of that file, but
not ASCII.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Oct 3 20:03:50 2006

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