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.

1 files changed, 4 insertions, 1 deletions

diff --git a/elisp/geiser.el b/elisp/geiser.el
index 774ee54..478b10c 100644
--- a/elisp/geiser.el
+++ b/elisp/geiser.el
@@ -8,9 +8,12 @@
 ;; have received a copy of the license along with this program. If
 ;; not, see <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5>.
 
-
+;;; Commentary:
+
 ;; Autoloads and basic setup for geiser.
 
+
+;;; Code:
 ;;; Locations:
 
 ;;;###autoload