summaryrefslogtreecommitdiff
path: root/elisp
diff options
context:
space:
mode:
authorJonas Bernoulli <jonas@bernoul.li>2020-02-25 14:32:18 +0100
committerJonas Bernoulli <jonas@bernoul.li>2020-03-27 21:38:45 +0100
commitf7483fd2e8eff2124db11939177cef8bc9732e7e (patch)
tree3d87dee2ee1fdd69be70ba152451c3c08a304646 /elisp
parent0355cd691ddef4b8fd840535452da2fa71a4f6ea (diff)
downloadgeiser-guile-f7483fd2e8eff2124db11939177cef8bc9732e7e.tar.gz
geiser-guile-f7483fd2e8eff2124db11939177cef8bc9732e7e.tar.bz2
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.
Diffstat (limited to 'elisp')
-rw-r--r--elisp/geiser-guile.el1
1 files changed, 1 insertions, 0 deletions
diff --git a/elisp/geiser-guile.el b/elisp/geiser-guile.el
index 7a29761..9fec9a8 100644
--- a/elisp/geiser-guile.el
+++ b/elisp/geiser-guile.el
@@ -11,6 +11,7 @@
;; Start date: Sun Mar 08, 2009 23:03
+;;; Code:
(require 'geiser-connection)
(require 'geiser-syntax)