Sven Erik Knop
2016-09-29 12:54:53 UTC
Still my favourite error message from the server.
... = all files and directories below the path
* = all files below the path (i.e. exclude '/' from the search)
...* is therefore redundant and can be replaced with *
Indeed, the pattern you seek is
....uasset
(note the fourth dot)
The reason why the type map does not complain is that the type map is not verified to that level when saved.
The ...* pattern in the type map works (and you will get the correct type). The reason for the error in 'p4 files' is that in the past commands like 'p4 files' took the wildcards as given and applied the rules sequentially, exploding the resulting map and slowing down the server. We have fixed this, but we liked the error message :-)
Cheers,
Sven Erik
--
Sven Erik Knop | Principal Consultant
Perforce Software <http://www.perforce.com/>
T: +44 1189 771020 <tel:+441189771020> | M: +44 7974 351514 <tel:+447974351514>
Visit us on: Twitter <https://twitter.com/perforce> | LinkedIn <https://www.linkedin.com/company/perforce-software> | Facebook <https://www.facebook.com/Perforce>
Join Perforce on Tour 2016 in a city near you!
London September 22 | Berlin September 29
Register early to secure your seat! <http://info.perforce.com/Perforce-on-Tour-2016.html>
perforce-user mailing list - perforce-***@perforce.com
http://maillist.perforce.
... = all files and directories below the path
* = all files below the path (i.e. exclude '/' from the search)
...* is therefore redundant and can be replaced with *
Indeed, the pattern you seek is
....uasset
(note the fourth dot)
The reason why the type map does not complain is that the type map is not verified to that level when saved.
The ...* pattern in the type map works (and you will get the correct type). The reason for the error in 'p4 files' is that in the past commands like 'p4 files' took the wildcards as given and applied the rules sequentially, exploding the resulting map and slowing down the server. We have fixed this, but we liked the error message :-)
Cheers,
Sven Erik
--
Sven Erik Knop | Principal Consultant
Perforce Software <http://www.perforce.com/>
T: +44 1189 771020 <tel:+441189771020> | M: +44 7974 351514 <tel:+447974351514>
Visit us on: Twitter <https://twitter.com/perforce> | LinkedIn <https://www.linkedin.com/company/perforce-software> | Facebook <https://www.facebook.com/Perforce>
Join Perforce on Tour 2016 in a city near you!
London September 22 | Berlin September 29
Register early to secure your seat! <http://info.perforce.com/Perforce-on-Tour-2016.html>
Posted on behalf of forum user 'David Yerkess'.
I am working on a tool to check if the FileType of files matches the Typemap
table and have come across something I don't quite understand.
Quote
Quote
Thanks.
--
http://forums.perforce.com/index.php?/topic/4971-senseless-juxtaposition-of-wildcards
_______________________________________________
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________I am working on a tool to check if the FileType of files matches the Typemap
table and have come across something I don't quite understand.
Quote
binary+l //...*.uasset
seems to work, but if I do an Fstat on that pattern I getQuote
Senseless juxtaposition of wildcards in '//...*.uasset'.
Does the Typemap use different parsing?Thanks.
--
http://forums.perforce.com/index.php?/topic/4971-senseless-juxtaposition-of-wildcards
_______________________________________________
http://maillist.perforce.com/mailman/listinfo/perforce-user
perforce-user mailing list - perforce-***@perforce.com
http://maillist.perforce.