From 3ceb31b71824e59e3f000edf7cb09ab86616d723 Mon Sep 17 00:00:00 2001 From: Jonas Bernoulli Date: Tue, 25 Feb 2020 14:32:18 +0100 Subject: Mark the beginning of code part of elisp libraries with Code: heading It's the convention and by following it we make a big step towards supporting outline navigation. The convention doesn't say much about what parts of the code are supposed to be part of that sections and what parts belong in a subsequent section. Here we put the `require' forms in this section and maybe some setup code, that's a popular approach. In most cases there was " " where we now insert "Code:". They both serve a similar purpose and we keep the former because some users depend on that for navigation. We even add this " " in libraries where it previously was missing. In some cases the permission statement was followed by a commentary, which obviously does not belong in the "Code:" section. In such cases add the conventional "Commentary:" section. --- elisp/geiser-base.el | 2 ++ 1 file changed, 2 insertions(+) (limited to 'elisp/geiser-base.el') diff --git a/elisp/geiser-base.el b/elisp/geiser-base.el index 95fdc03..327a91f 100644 --- a/elisp/geiser-base.el +++ b/elisp/geiser-base.el @@ -10,6 +10,8 @@ ;; Settings and vars shared by all geiser modules, including little ;; utilities and emacsen compatibility bits. + +;;; Code: ;;; Emacs compatibility: (require 'ring) -- cgit v1.2.3