geiser/elisp/geiser-popup.el, branch 0.33emacs and scheme talk to each otherhttps://jao.io/cgit/geiser/atom?h=0.332024-07-06T15:37:23ZCleanup library headers2024-07-06T15:37:23ZJonas Bernoullijonas@bernoul.li2022-07-14T12:33:38Zurn:sha1:de52f0e36f1709181c1ce4e787d79208fa2cb870
- In the summary line, use three dashes to separate the file name
from the summary. That is the convention, which some tools depend
on, and for some libraries we already did it here too.
- Capitalize the first word in the summary. That is the convention,
and for some libraries we already did it here too.
- For libraries that have a commentary, make sure it is placed in a
"Commentary:" section.
- Make sure the "Code:" heading, which separates the header from the
code part of the library, exists in all files.
Use lexical-binding2023-12-15T21:33:58ZJonas Bernoullijonas@bernoul.li2023-12-15T21:29:45Zurn:sha1:b20dd4d77b92197d88d7cf3512fe202581d5c430
Emacs 30.0.50 has started to warn when this variable isn't set,
presumably so that the default can be changed from nil to t in
a few years.
I see no reason not to use lexical-binding.
Fix indentation2020-03-27T20:38:45ZJonas Bernoullijonas@bernoul.li2020-02-25T13:48:04Zurn:sha1:a11b96fe58a2579e15bfcb642f01e0059da59a87Mark the beginning of code part of elisp libraries with Code: heading2020-03-27T20:38:45ZJonas Bernoullijonas@bernoul.li2020-02-25T13:32:18Zurn:sha1:3ceb31b71824e59e3f000edf7cb09ab86616d723
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.
Begin the summary lines of all elisp libraries with three semicolons2020-03-27T20:38:45ZJonas Bernoullijonas@bernoul.li2020-02-25T13:29:01Zurn:sha1:715f4c0ee0f50b251679e55650cedcae3a246b57
It's the convention and by following it we make a big step towards
supporting outline navigation.
Add a (declare (debug)) form to all geiser-%s--with-buffer macros.2019-09-03T07:06:02ZLockywolflockywolf@gmail.com2019-08-28T03:12:35Zurn:sha1:c8daa71db73e6f9bfbf9b7d23477d8e885fe8d64A couple of byte-compilation warnings gone2013-07-01T19:39:10ZJose Antonio Ortega Ruizjao@gnu.org2013-07-01T19:39:10Zurn:sha1:ae7bb5d6ff1595a28557d7cda2416e1cbce680f3Whitespace2012-10-11T02:17:35ZJose Antonio Ortega Ruizjao@gnu.org2012-10-11T02:17:35Zurn:sha1:b8630ca33b9abbcc5b39163d1df9180a66f1f998Avoiding old-style backquotes during compilation of geiser-popup.el.2010-07-08T18:43:11ZJose Antonio Ortega Ruizjao@gnu.org2010-07-08T18:43:11Zurn:sha1:97b953d0bbf6162ab15ccff8af0b9891922ab491Better keybindings for documentation browser2010-06-14T20:31:13ZJose Antonio Ortega Ruizjao@gnu.org2010-06-14T20:31:13Zurn:sha1:c9d76d4770ffc21aae81692a213b48b9e86315a1