We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently a key=value pair in the configuration files letmein.conf and letmeind.conf cannot span multiple lines.
key=value
letmein.conf
letmeind.conf
Allow line continuation by backslash-escaping of newlines. Example:
[FOO] bar=baz\ biz
shall be equal to
[FOO] bar=baz biz
Care must be taken to not interpret continuation lines starting with # as comments.
#
[FOO] bar=baz\ # biz
[FOO] bar=baz# biz
Long lines can be broken down and be made more readable. This could be especially useful for the [RESOURCES] section.
[RESOURCES]
It is not fully compatible with existing configurations. An existing configuration might use a literal backslash at the end of the line:
[NFTABLES] exe = /foo/bar\
This would currently mean exe is equal to the string /foo/bar\.
exe
/foo/bar\
However, this probably is only a theoretical problem.
bar=biz\\
biz\
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Status Quo
Currently a
key=value
pair in the configuration filesletmein.conf
andletmeind.conf
cannot span multiple lines.Suggested enhancement
Allow line continuation by backslash-escaping of newlines.
Example:
shall be equal to
Care must be taken to not interpret continuation lines starting with
#
as comments.shall be equal to
Pros
Long lines can be broken down and be made more readable. This could be especially useful for the
[RESOURCES]
section.Cons
It is not fully compatible with existing configurations.
An existing configuration might use a literal backslash at the end of the line:
This would currently mean
exe
is equal to the string/foo/bar\
.However, this probably is only a theoretical problem.
Open questions
bar=biz\\
would yield the valuebiz\
The text was updated successfully, but these errors were encountered: