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

Re: [TSVN] log messages during update process truncated

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2005-08-10 08:48:46 CEST

SteveKing wrote:
> Ulrich Eckhardt wrote:
> > I do admit that I have rather longish paths so partially this is also my
> > fault. However, when I run update on some deeply nested directories, it
> > sometimes happens that the path/message is truncated.
> >
> > In that context, I would find it extremely cool if you could clip paths
> > so the common part of all paths is omitted. E.g. if I trigger an update
> > on "C: \Dokumente und Einstellungen\eckhardt\Eigene
> > Dateien\evc4\common-build-env\development\" only "..development\"
> > remains.
>
> Do you mean the paths shown as 'updated', 'merged', 'deleted', ...?

When it shows just on of these in the first and a path in the second column,
the path is AFAICT complete.

> Or paths shown in error messages?

In these cases, the error-message is sometimes truncated, because
"<really-long-path> failed to do this or that with" is probably too long for
the column.

> If the first, then you can simply resize the columns to see the paths.

Yes, I know. ;)

Seriously, the structure I use is really deeply nested (I will have to move a
few things) so that for some items SVN itself fails - probably a MAX_PATH
issue. For some paths for which SVN still works, an error (like e.g. a
conflict) enlarges the content of the second column so far that the whole
message is truncated. Could it be that I'm hitting a limit of MS Windows'
listboxes or that you are using a too small static buffer for the output?

Uli

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 10 09:03: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.