> -----Original Message-----
> From: Gerald Britton [mailto:gerald.britton_at_gmail.com]
> Sent: Saturday, December 03, 2011 10:35 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: RE: AW: Re: Export folder dialog
> > How do you know this? Unless you have the source code and probably a
> > history of what the program has done up to the point you specify the
> > path I don't think it's possible to know what R:foo means.
> Seriously? You can't mean that I should consult the source to Tortoise
> SVN before using one of its functions, can you?
I think you are missing the point. R:foo is relative to the current
working directory. The current working directory is set using a windows
API. Tortoise runs in the context of Windows Explorer. Windows explorer
might use this API, Tortoise might use this API, and anything else that
runs in the same context (other plug-ins, etc) may use this API. The
last call wins.
I am not arguing that there isn't a bug here. I am just pointing out
that using a relative directory in this context might result in
unpredictable results. You are more than welcome to leave of the '\' but
don't be surprised if you get random or incorrect results.
> > Have you tried the operation with an explicit destination?
> Yes, I navigated the tree hierarchy in the export window to the
> destination directory and the export was successful.
> For example
> > r:\foo. If there is a small number of files exporting to r:foo might
> > complete before the dialog box pops up.
> there are a number of large files. When the export works, it takes
> 30 seconds. When I just type R:foo into the Folder field, it
This is helpful information. Before I replied to you I tried exporting a
small directory and saw the export dialog for only a brief moment. Since
I am using a 5 year old computer it's quite possible that it might be
missed on a faster computer.
> >AND since you really have no way
> > of knowing what r:foo means at any given point in time
> Sure I do! Open a command prompt and type R: and pwd. I can see that
> it is at the root of the share.
I am pretty sure that the current working directory for each drive
letter is tracked per process. Type 'cd r:\foo' open a new command
prompt and then type r:. You'll notice each process has a different
value for pwd.
Now try this. Open up the run dialog and enter this command 'cmd /K
"r:"'. Your command prompt will probably look something like this
'R:\>'. Now type 'C:'. Does your prompt look like 'C:\>'? My guess is
that it does not.
Explorer is much more complicated. Maybe it never sets the working
directory so it's always the default. R:foo works great but then you
install Joe's nifty Explorer plug-in that cures world hunger. For some
reason Joe's plug-in sets that working director to 'r:\bar' and now
'r:foo' turns into 'r:\bar\foo'.
> >you would need to
> > search the while entire R drive to verify the that export did not
> > happen.
> I don't think so, no. The exported files would either be in the
> directory R:\foo, if the cur. directory of R: is root (it is), or in a
> folder called foo off the current working directory, if not root.
> There are no other options, I think.
> > Don't take this wrong. I do not know whether a problem exists or
> > am just pointing out that we (members of the mailing list) don't not
> > have enough information to really figure what might be going on.
> I wonder, has anyone else tried this as I described to see what their
> results might be?
I did notice that the version of Tortoise SVN (TortoiseSVN 1.6.10, Build
19898) that I am using tells me that
'c:foo' is an invalid directory. I get the same message whether foo
exists or not. This seems reasonable to me since c:foo is kind of
It's possible that the 1.7 version also rejects that path later on but
doesn't produce and error message.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-12-05 19:38:23 CET