On 14.11.21 00:18, Branko Čibej wrote:
On 13.11.2021 00:05, C. Michael Pilato wrote:
WARNING: This is a /total/ drive-by post as I skim the thread.
Are there any svn:auto-props syntaxes that are legal .ini but not
legal for auto-props? I'm thinking of the use of a forward slash
character. Could the format be extended such that a key/propname
under the [auto-props] section that starts with '//' (convenient
comment-esque) indicates some parsing option flag?
*[auto_props]*
*// accept_gnu_extension = true*
*// some_other_keyword_that_does_something_else = 3.14
!(CMakeLists).txt = svn:mime-type=text/plain
CMakeLists.txt = svn:mime-type=text/x-cmake*
Another total drive-by, as I'm not actually looking at the code right
now: but if memory serves, we just look for the separator (= or :) and
accept anything from the start of the line to there as the property name.
This is even documented:
https://cwiki.apache.org/confluence/display/SVN/Configuration+File+Syntax
There's a formal syntax definition there, so anyone who wants to
introduce extensions can check them against those rules.
-- Brane
This config file documentation reminds me on the case problem regarding
auto-props. Like *.c and *.C may need different properties but that
can't be configured right now.
What about adding an auto-props file containing the rules and having a
better suited format. An entry in the configuration could switch between
old style auto-props section and new style auto-props file.
- Martin
