Quoth Tobias Schäfer:
> Using /path when the file should be deleted afterwards and
> alternatively /tempfile when the file should not be deleted by tortoiseproc
> seems a bit confusing to me. I prefer always using /path for the path and
> optionally passing /tempfile if it is a tempfile. TortoiseProc then knows
> it needs to delete the file.
No, no, you seem to have misinterpreted what I said :)
What I meant was:
1. the temp file passing mechanism used by the shell extension is
utterly forbidden from using /path to pass its temporary filenames in.
Instead, it uses a new parameter called /tempfile wherever it used to
use /path, thereby freeing up /path for the automation interface.
2. the existing automation interface should remain [almost] completely
unchanged. /path should still be used to pass the paths for any
automation command -- the *only* differences are that:
(a) /notempfile is now optional (won't barf, and doesn't make any
difference if it's specified or not)
(b) under no circumstances are anything specified in /path deleted,
since that option is no longer used for temp file passing.
Ergo, anything passed via /tempfile is always deleted, and anything
passed via /path is never deleted.
> It can actually also contain directory names, so /pathlist would be better.
>
> Renaming /path to /pathlist (or filelist) will break all calls of
> tortoiseproc which users have created to automate TSVN. I definitely don't
> want to do this!
I think this all stems from the original misunderstanding. I'm
referring to the shell extension's temporary files here, not the
automation interface.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Sep 25 08:34:43 2006