geiser/elisp/geiser-xref.el, branch 0.33emacs and scheme talk to each otherhttps://jao.io/cgit/geiser/atom?h=0.332024-07-06T15:37:23ZButtons live in their own namespace2024-07-06T15:37:23ZJonas Bernoullijonas@bernoul.li2022-08-12T13:07:18Zurn:sha1:f74612686b468069849ab36d1c49229312f3434e
`geiser-doc--xbutton' will be tackled in the next commit.
Cleanup 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.
Take the byte-compilers advice into account2022-12-05T14:17:55ZJonas Bernoullijonas@bernoul.li2022-12-05T14:17:55Zurn:sha1:a60efa80cdb8c72dacb1e16729a801206a4e80bfgeiser-xref: lexical binding2022-10-23T23:33:57Zjaojao@gnu.org2022-10-23T23:33:57Zurn:sha1:8009febe4cc7d9ad1e8826dc2a1ee3e4c336f315Harmonizing buffer names2022-03-06T19:18:54Zjaojao@gnu.org2022-03-06T19:18:54Zurn:sha1:f9a40fe67e15ad2ec984687a8e99844707f736e5
So that now all start with *Geiser (and a space for hidden ones) and
use consistent capitalization (see issue #38).
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.
Define 'geiser-xref-mode' with 'define-derived-mode'2016-04-23T00:20:25ZAlex Kostalezost@gmail.com2016-04-11T07:54:48Zurn:sha1:ea1c6ece98a88ef66b4bdbf286cc3df603bfa7e7Do not use 'geiser-xref--with-buffer' before it is defined2016-04-20T17:39:07ZAlex Kostalezost@gmail.com2016-04-11T16:26:17Zurn:sha1:78d5866d16f2718ddffe1c0646fc59cffe785d9b
This is a fix similar to the one made in commit
8e75455dfbd46355d777c26366e7ccfcb59ace20.