Pádraig Brady

Indeed. This is due to the matching name (alma) in the default/global section. The code has this comment: ``` # XXX: Note this strips an item from section # if...

The reason for this is that global/DEFAULT entries auto propagate to all other sections. Therefore entries in other sections that have the same value are redundant, and so not listed....

More accurately crudini does support multiple sections of the same name, but will merge the keys in each section, and so only show the last value for each duplicated name....

Right, we explicitly disallow that since commit 50718ed6, as without that commit we could read and write existing section contents containing extra [ ... ] but we can't write new...

Indeed that's a bug that should have been handled when implementing issue #38 Thanks for the clear reproducer. It should be easy enough to address

What's going on here is that in ini files, keys in the global section are returned as keys in each section. Therefore we have logic to strip keys from each...

This would overlap with supporting lists. I.E. EXAMPLE.COM is a multiline item, and we might support editing items in the list. Anyway currently deleting the curly brackets gets you a...

This is a good idea as the formats are close. In general it would be good to support filters to adjust to/from ini format, so you could `crudini --filter=ssh` to...

`--format=lines` was added to give general flexibility like that. With some caveats on the format of the values, something like this might suffice, to give unique section_param=value items: eval $(crudini...

Unfortunately "standard" ini file format treats leading whitespace specially, as it's used to create multiline values, hence the iniparse library that crudini uses is giving an error. I see indented...