Skip to content

Commentary #18

Open
Open

Description

@canweriotnow

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?

Activity

  1. yurrriq commented on Jul 28, 2015

    @yurrriq
    Member

    It might be good to have a description of how to set up Flycheck too!

  2. canweriotnow commented on Jul 28, 2015

    @canweriotnow
    ContributorAuthor

    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.

  3. stale commented on Jun 5, 2017

    @stale

    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.

  4. added a commit that references this issue on Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions