[suggestion] ini format should follow standard

Question

[suggestion] ini format should follow standard

Opened this issue 11 years ago · 8 comments

'.ini' extension name is better than '.wini' to let vim/other editors happy without exta settings.
'=' is better then ':=', that let vim syntax highlight work better. And it save the time of typing.
I assume https://github.com/vaughan0/go-ini could help you to parse ini file

Answer 1 · 2013-09-04T00:46:34.000Z

I fully admit that I made a poor decision initially, but I wanted to have simple variable substitution. In retrospect, that feature didn't turn out to be so useful. If I switch to anything, it will be toml. But switching is difficult, and would require every user to update their config files.

This isn't me saying "no", but it is me saying, "yeah, would be nice, but it just isn't a priority right now."

Answer 2 · 2013-09-04T00:46:42.000Z

I just understood .wini has its purpose of assign variable. That's another issue to provide syntax hightlight for vim.

Answer 3 · 2013-09-04T00:49:10.000Z

Honestly, I'm not at all concerned about syntax highlighting. That has absolutely no bearing on my decision. Particularly since most of the config files are bindings to gribble commands, which has no syntax highlighting at all.

Answer 4 · 2013-09-04T00:55:09.000Z

I agreed. So, close this issue, and if one day gribble have someone provide 3rd party syntax highlight file. Then it works.

Answer 5 · 2013-09-04T00:56:47.000Z

Leaving it open. I've actually been wanting to do this for a while already. It would remove a boat load of code from Wingo, which is a win. I'm just not sure when it will happen.

Answer 6 · 2013-09-04T09:07:14.000Z

@dlintw You can easily just switch on the highlighting mode for the file you're in? I'm not a Vim user but in Emacs switching highlighting modes is trivial.

@BurntSushi One possible idea is to support both formats (or even a multitude of formats) instead of a single one. Explain the hierarchy of formats and allow users to choose. More work on your part but less annoyance for users.

Answer 7 · 2014-06-07T03:43:08.000Z

I found the natural meaning of the setting file is different. As .ini format, every variable can assign once, and the latter will overwrite first. But in wingo's config files, it will do all the actions.

Answer 8 · 2014-06-07T03:50:01.000Z

Yes. wini is not ini. Wingo's config situation is very unfortunate, but I'm not breaking backwards compatibility at this point until a Wingo 2. At which point, I'll be rethinking config entirely.