On 9 November 2011 13:57, Gerald Britton <gerald.britton_at_gmail.com> wrote:
>> Hi, Gerald,
>> Von: Gerald Britton [mailto:gerald dot britton at gmail dot com]
>> > Is it reasonable to ask TSVN to remove trailing blanks for the ignore list? It's an easy mistake to make and appears invisible until you really look for where the line ends.
>> This will prevent users from adding filenames with trailing spaces to the ignore list.
>> Apart from that, silently mangling the users is never a good idea.
> I would agree, except that apparently TSVN and SVN behave differently in this regard. That is, if my ignore list includes:
> *.foo \n
> with a space before the line end, I'm seeing TSVN put a minus (-) sign in the icon in explorer for bar.foo -- indicating it is being ignored. OTOH, SVN does _not_ ignore this file, so it appears in the commit dialog.
> So I guess what I'm really asking is, shouldn't TSVN behave like SVN and *include* blanks before the line-end as part of the filename?
You seem to be confusing TSVN and SVN. SVN is a command line client
and has no commit dialog. The commit dialog is part of TSVN, so if the
commit dialog says it is unversioned then that is its subversion
status. That means that TSVN is taking account of the blank and not
ignoring the file, which is expected since it is the SVN library, not
any TSVN code, which decides whether a file is ignored or not.
It sounds more like you are having a problem with icon overlays which
can happen if there are not enough overlay slots available in Windows
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-09 23:18:40 CET