dunst/test/data/test-ini
Luke Shumaker a7b3ff1ea8 Handle "\n" -> newline expansion in the option_parser.
It makes more sense to handle escapes in configuration strings when we
parse them, rather than after-the-fact when we handle notifications that
use the relevant config options.

Do this in the proper backslash handler; rather than a naive string
replace which doesn't allow the backslash to be escaped (`\\n` => 0x5C0x0A
rather than 0x5C0x6E).
it to the proper backslash handler
2017-02-28 16:49:09 -05:00

49 lines
1.1 KiB
Plaintext

#General comment
[bool]
booltrue = true #This is a test inline comment
booltrue_capital = TRUE
#This is a comment
boolfalse = false
boolfalse_capital = FALSE
boolyes = yes
boolyes_capital = YES
boolno = no
boolno_capital = NO
boolbin0 = 0
boolbin1 = 1
boolinvalid = invalidbool
[string]
simple = A simple string
simple_with_hcomment = A simple string # a comment
simple_with_scomment = A simple string ; a comment
simple_with_nl = A simple string\nwith newline
quoted = "A quoted string"
quoted_with_hcomment = "A quoted string" # a comment
quoted_with_scomment = "A quoted string" ; a comment
quoted_with_nl = "A quoted string\nwith newline"
quoted_with_quotes = "A string \"with quotes\""
quoted_with_escapes = "A string \\\"with escapes\\"
quoted_with_cchar = "A string; with #comment characters" # a comment
quoted_in_middle = A string"; with #comment" characters # a comment
escaped_quotes = String \"with quotes\"
[int]
simple = 5
negative = -10
decimal = 2.71828
leading_zeroes = 007
multi_char = 1024
[double]
simple = 1
decimal = 1.5
negative = -1.2
zeroes = 0.005
long = 3.141592653589793