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-connection.el | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'elisp/geiser-connection.el') diff --git a/elisp/geiser-connection.el b/elisp/geiser-connection.el index 510afe9..4fb7363 100644 --- a/elisp/geiser-connection.el +++ b/elisp/geiser-connection.el @@ -9,11 +9,14 @@ ;; Start date: Sat Feb 07, 2009 21:11 - +;;; Commentary: ;; Connection datatype and functions for managing request queues ;; between emacs and inferior guile processes. + +;;; Code: + (require 'geiser-log) (require 'geiser-syntax) (require 'geiser-base) -- cgit v1.2.3