Skip to content

Commentary #18

Open
Open
@canweriotnow

Description

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?

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