Rudder

Rationale :

Many configuration files have a format “Key value” with any arbitrary combination of spaces and/or tabs as a separator.

The actual configuration files present on any given node can contain any combination of these, and this is not predictable, especially if such files have already been edited.

The current implementation of the “File key-value present” (+ with option) generic methods doesn't allow to specify a separator that could be either a space OR a tab.

We have the ${const.s} and ${const.t} constants that respectively represent space and tab, but no constant to represent any kind of space.

This is a limitation, and has already popped up in customer assistance.

So we would either need a new constant representing any combination and length of “spaces or tab”, or far better a GUI box to specifiy that the wanted separator is any of them.

(For in support experience it seems that few customers are aware of the existence and use of ${const.s/t/dollar} special constants.)