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, 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)