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

Request: Add MiSTer_example.ini #46

Open
Natrox opened this issue Feb 18, 2023 · 3 comments
Open

Request: Add MiSTer_example.ini #46

Natrox opened this issue Feb 18, 2023 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@Natrox
Copy link

Natrox commented Feb 18, 2023

Hello,

We've had a number of people run into INI errors because they used a clean one from the Main_MiSTer GitHub page.

The INI present in that repository often has options not yet available in the public release.

While these errors aren't fatal, I think it would be nicer if users had a clearer source for a clean INI.

My suggestion is to add a "MiSTer_example.ini". This INI would be matched to the distribution version of the main binary - and could contain some text at the top like "Copy this file and rename it to MiSTer.ini to use".

Adding this would give users an easy location to find a fresh INI, with the added benefit of being available offline.

@Dinierto
Copy link

I like this idea it's a good stop gap measure that doesn't require overwriting or parsing existing INI files but allows for end users to easily grab the latest version

@kurohouou
Copy link

This is exactly how it should be, the ini here should follow the public release!

@theypsilon
Copy link
Member

I think is a good idea. I'm not sure about in which repository this should go. But if somebody would like to provide and maintain that "MiSTer_example.ini" he could open a PR to the 'develop' branch of this repository by now.

I can't commit to maintain it, but I can commit to support it, thus I'm tagging this issue with the help-wanted label.

@theypsilon theypsilon added the help wanted Extra attention is needed label Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Development

No branches or pull requests

4 participants