Bump.
Quoth Gavin Lambert:
> Quoth Gavin Lambert:
>> 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.
>
> ie. where it may previously have used:
> /path="path\to\users\temp\folder\blaargl.foo"
> it now uses:
> /tempfile="path\to\users\temp\folder\blaargl.foo"
>
> /tempfile is a data parameter rather than a switch. It sounded like you
> were originally proposing it as a switch, continuing to use /path for
> the actual data, which just seems wrong. (Because then sometimes /path
> would be deleted and sometimes it wouldn't be, which seems ugly.)
>
>
> It does sort of depend on exactly how the shell interface works. The
> impression I've gotten from the discussion thus far is that the 'temp
> file' contains all the information necessary to carry out the command in
> some internally-defined format, so that if the shell is passing
> /tempfile=whatever then it doesn't need to pass any other parameters at
> all.
>
> If that's not the case, and the shell is using exactly the same
> automation interface as everyone else, then perhaps a simple switch
> makes sense. But that didn't seem very likely since in the automation
> interface the /path directly indicates which files to
> export/commit/whatever, whereas in the shell case it seems to be a
> temporary file, which seem like mutually exclusive uses.
>
>
> When I suggested '/filelist' or something similar (though probably
> '/listfile' makes more sense, come to think of it), I was thinking that
> some program which is currently passing things like this:
> TortoiseProc .... /path="file1 file2 file3 file4 ..."
> might instead want to create a file containing the paths one per line,
> and then do this instead:
> TortoiseProc .... /listfile=list.txt
> where Tortoise would read the contents of the given file and then use it
> as if it had been passed as a /path parameter. (And without deleting
> the named file, unless it was also named in /tempfile. But that's a
> separate issue.)
>
> That was essentially a completely separate suggestion from the whole
> tempfile changing thing. Sorry for any confusion that may have caused :)
>
> Although if that existed, then potentially the shell interface could be
> changed to use that along with the standard /command interface, and
> remove the whole confusing separation once and for all. Then /tempfile
> would merely be a "delete this when you're done" indicator and not a
> "delete this when you're done, and also use it to do this whole separate
> command interface".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Sep 29 08:43:28 2006