summaryrefslogtreecommitdiff
path: root/elisp/geiser-chez.el
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
commit591c794e828ed2d8a3211a3e152ea3bf8858ba0e (patch)
treebab67561b994fedcdd79dec1adbb0bf3451434ef /elisp/geiser-chez.el
parent352515c3aa12c9ebbdd997e5ab061ad182a45958 (diff)
downloadgeiser-chez-591c794e828ed2d8a3211a3e152ea3bf8858ba0e.tar.gz
geiser-chez-591c794e828ed2d8a3211a3e152ea3bf8858ba0e.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/geiser-chez.el')
-rw-r--r--elisp/geiser-chez.el3
1 files changed, 3 insertions, 0 deletions
diff --git a/elisp/geiser-chez.el b/elisp/geiser-chez.el
index 601cc6f..8eabae6 100644
--- a/elisp/geiser-chez.el
+++ b/elisp/geiser-chez.el
@@ -5,6 +5,9 @@
;; have received a copy of the license along with this program. If
;; not, see <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5>.
+
+;;; Code:
+
(require 'geiser-connection)
(require 'geiser-syntax)
(require 'geiser-custom)