Hi! I'm encountering some .ini/.conf files with spaced sections, like in this post:
[Repository LocalExample]
type = Maildir
localfolders = ~/.maildir/example
utime_from_header = yes
filename_use_mail_timestamp = yes
and I see that your library parsing these to keywords results in case-insensitive barred spaced key: :|REPOSITORY LOCALEXAMPLE|. Sections are often case-sensitive and may contain spaces, so this behavior is suboptimal. Any reason it's implemented this way?
An alternative would be to consider section names (and maybe even setting keys) as opaque strings. Which would work with most expectations, but would be slightly less lispy. Any thoughts on that?
Hi! I'm encountering some .ini/.conf files with spaced sections, like in this post:
and I see that your library parsing these to keywords results in case-insensitive barred spaced key:
:|REPOSITORY LOCALEXAMPLE|. Sections are often case-sensitive and may contain spaces, so this behavior is suboptimal. Any reason it's implemented this way?An alternative would be to consider section names (and maybe even setting keys) as opaque strings. Which would work with most expectations, but would be slightly less lispy. Any thoughts on that?