Add an indication of some type, after the readme has been printed, to inform the user what exercise they are currently at and how far they have until completing everything.

Maybe a visual indication too. 🤔

Here's an always updating list of exercises and features we must implement to get this project cooking.

Features

• Print markdown to terminal.
• Pytest integration (some exercises will make use of pytest to test the answers/values)
• Command to update exercises folder with new exercises.

Exercises to implement.

This list is heavily inspired by Rustlings, in fact most of the exercises are basically from Rustlings.

Whatever is in brackets are notes. If you see the letter "E", it is referring to "Exercise" so whatever number comes after that is the exercise id we are referring to.

• Fix this print statement. (after E1)
• Print "Hello, World!" from scratch. (no prior code given, should be after E1)
• Assign a string with the value "Hello" to this variable. (below the variable should be printed with a random name, should be after E3)
• Change this number into a string. (after E4)

As the title says we must add some install and usage instructions to the readme, however they must be well written and obvious as many beginner developers will be reading and relying on theses instructions.

Ideally they should install snekilings with pip, create a folder and sneki init to create the exercises folder then run sneki start to begin working on the exercises and etc.

As the title says. There's just many places in the source code and exercises where the old "snakelings" name was used.

When you remove the I'm not done yet it should run the code to test what you have done is correct which it does but if your result is incorrect and you then correct it later, save the file, it seems to state the the answer is still wrong even though it's correct. Try it and you'll see what I mean.

Reproduce steps

1. Run snakelings for the 2_math exercise you made.
2. Remove the I'm not done yet comment, save the file. (it should error once again, which is good as the answer is incorrect)
3. Solve it correctly now then save the file.
4. It won't continue off, it will continue to give you the same pytest error.