-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
specificity of emacs lisp exercises #104
Comments
While I love this idea in theory, I think in practice this might have some broader reaching implications for the wholistic exercism ecosystem, and I'm not sure that its been done with any of the other tracks. I think that many of the exercises in the elisp track however can be approached from an angle that is more "emacsy" (like preferring buffer data-types over string data-types for example.) Im curious what input @iHiD and @kytrinyx would have on this issue, and even more curious to know if it has come up in other tracks before. |
We have a track that has all custom exercises (Ballerina: http://github.com/exercism/ballerina). It's certainly possible. (I need to write up proper documentation for how it's done, though). It's also possible to customize the description of the generic exercises. Here's some stuff about custom exercises: Here's some stuff about overriding generic metadata: I think that a combination of tackling the standard exercises from an emacs-y angle and having custom exercises in addition would make sense. |
That's really good news. I'll try to go through the links you gave and see if I can be of any help there. |
Awesome, holler if it's confusing (I'm sure it is, unfortunately. My plan is to overhaul all of the documentation over the end-of-year holidays). |
This should be best addressable through Concepts / Learning exercises now. |
I took a casual look at the list of available exercises and was surprised by the fact that none of them were addressing the domain in which Emacs Lisp is most likely to be used: Emacs and its specific data types (buffers, etc.).
The text was updated successfully, but these errors were encountered: