Skip to content
New issue

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

groups with differnt parent but same name get ommitted #24

Open
mjrk opened this issue Nov 17, 2014 · 2 comments
Open

groups with differnt parent but same name get ommitted #24

mjrk opened this issue Nov 17, 2014 · 2 comments

Comments

@mjrk
Copy link

mjrk commented Nov 17, 2014

In my terminator config I had a [profile] and a [layout] sub-group with name "[[default]]". After reading and writing the config with ruby-parseconfig, only the first entry will be left. The config results corrupted (because of one or more missing parent nodes) and terminator won't be able to load it.

I interpreted 'It also supports nested [group] sections.' as the way some gnome config files have nested groups by multiple '[',']' for every level. But it seems there isn't a hierarchical implementation of groups. Are you planning to add this feature, if so in which way? If not, maybe a small readme update might reduce confusion.

@derks
Copy link
Member

derks commented Nov 18, 2014

@mjrk thanks for the feedback and issue report. The nested groups, are those groups designated by the [brackets] ... as the primary config is not under a bracket/nested group.

I do not actually develop in Ruby anymore, and find it hard to maintain this library properly. I've been hoping someone will come along that uses the library, and would be interested in helping improve it... but have not had any interested as of yet. I'll try and spend some time here over the next few weeks to improve things and get the next release out.

@mjrk
Copy link
Author

mjrk commented Nov 19, 2014

I see, so it can only be nested one level under the primary config. Currently there are some other projects with priority, maybe I will find time to improve parseconfig the next time I use it. Anyway thanks four your great work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants