On top of what is explicitly stated in Golly documentation, I suggest to choose some filename that doesn't contain two consecutive delimiters anywhere (in other words, neither of '--', '-_', '_-', '__' is a substring), and doesn't start or end with a delimiter.b-engine wrote: September 29th, 2024, 5:59 pmI see. I may rename the rule to B--Univ, but this could cause confusion with B-Univ.dvgrn wrote: September 29th, 2024, 11:55 am Rule names with special characters cause various subtle but time-consuming maintenance headaches. You might not have to do any of that annoying maintenance yourself -- but other people (like me) do. Which is why we're asking you to please make a simple easy change to your rule names.
Even though Golly documentation doesn't explicitly prohibit two or more consecutive hyphens (as in your suggested replacement), I think it's fairly clear that the main intended use of hyphens in @RULE file names doesn't involve any such sequences of consecutive hyphens, see the quoted parts below:
Golly documentation wrote:To allow for possible future extensions in the way Golly handles rule names, it's best to use only letters and digits. Hyphens and underscores are also okay if you need some sort of separator. Hyphens can allow a set of related rules to share colors and/or icons (see below). Note in particular that spaces and colons must not be used.
[...]
If rulename.rule is missing either the @COLORS or @ICONS section, Golly checks to see if rulename contains a hyphen. If it does then it looks for the missing color/icon data in another .rule file called prefix-shared.rule where prefix consists of all the characters before the final hyphen. (As in the above searches, it looks in your rules folder first, then in the supplied Rules folder.) This allows related rules to share a single source of colors and/or icons.
