| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
It's the convention and by following it we make a big step towards
supporting outline navigation.
|
|
Seems we forgot a require while adding a new defcustom in geiser-log.
|
|
|
|
|
|
|
|
|
|
A couple functions to manage logs, and a fix to the definition of
geiser-messages-mode: do not ever kill all local variables in a
derived mode definition!
|
|
|
|
Set geiser-log-verbose-p to t to enable all logs. Calling
geiser-show-logs with a prefix argument will do that for you.
|
|
|
|
|
|
|
