emacs-lisp

Emacs Lisp style guides establish conventions for readability and consistency: 80-character line limits, 2-space indentation, kebab-case naming, lexical binding, thorough docstrings, and autoload cookies. Following these standards ensures your configuration files, packages, and interactive commands work reliably across Emacs environments and remain easy for others to understand and maintain.

Emacs Lisp naming conventions use kebab-case for public symbols, private-function prefixes to denote internal helpers, and predicate-naming suffixes (e.g., `-p` for boolean-returning functions). Consistent naming improves code clarity, prevents namespace collisions, and makes your packages compatible with Emacs ecosystem expectations.

Autoload cookies defer function loading until first use, reducing startup time. Place autoload directives above function definitions, use lexical binding at the file header, and structure your package with public entry points and private helpers. This approach enables faster Emacs initialization while keeping full functionality available on demand.

Lexical binding restricts variable scope to their definition block, improving performance and predictability. Enable it with `lexical-binding: t` in your file header. Dynamic binding searches the call stack, which is slower and error-prone. Modern Emacs Lisp development favors lexical binding for cleaner, more maintainable code.

Structure packages with modular organization, module headers describing purpose, comprehensive docstrings for all public functions, autoload cookies for interactive commands, and private symbol conventions. This combination ensures users can quickly understand your package, load it efficiently, and extend it safely without namespace conflicts.