Skip to content

Accomodate for spaces in section names (maybe use strings for section names?) #2

Open

Description

@aartaka

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions