Commentary #18
Labels
Comments
|
It might be good to have a description of how to set up Flycheck too! |
|
Yes 👍 to setting up Flycheck. I think I suggest using emacs-prelude for new users in my help guide, which comes with flycheck installed and configured, but a separate guide would be good. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
fapdash
added a commit
to fapdash/exercism--emacs-lisp
that referenced
this issue
Oct 21, 2022
- split up into different sections, accommodate people just starting out with Emacs a bit more - add installation instructions for starter kits - add Doom Emacs starter kit for people switching from vim - reference style guide and coding conventions closes exercism#198 works on exercism#18 (exercism#18 (comment))
This was referenced Oct 21, 2022
ErikSchierboom
pushed a commit
that referenced
this issue
Oct 26, 2022
* Improve "Learning Emacs Lisp" doc - split up into different sections, accommodate people just starting out with Emacs a bit more - add installation instructions for starter kits - add Doom Emacs starter kit for people switching from vim - reference style guide and coding conventions closes #198 works on #18 (#18 (comment)) * Minor fixes from proof reading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since elisp packages have a very structured and opinionated format, requiring a
;;; Commentary:section, it might be good to add some language-specific guidance for each exercise here. I'll update with a running checklist of exercises that have/need commentary, but I figure if Emacs says do it, and it could be helpful to users, who am I to argue?The text was updated successfully, but these errors were encountered: