geiser/elisp, branch 0.24emacs and scheme talk to each otherhttps://jao.io/cgit/geiser/atom?h=0.242022-05-07T00:34:25ZVersion bump2022-05-07T00:34:25Zjaojao@gnu.org2022-05-07T00:34:25Zurn:sha1:d28d19b582347bffebbf0ca905297e744842a5f2geiser-capf: new module to break cyclic dependencies2022-04-23T18:05:57Zjaojao@gnu.org2022-04-23T18:05:57Zurn:sha1:1b1fdd2be47fcbadab4b224266d30dee4484a4b0Suggestive patch for simplified completion2022-04-23T15:01:15ZDaniel Mendlermail@daniel-mendler.de2022-04-02T00:19:54Zurn:sha1:18faa0ba32c9ce751c16960b2a39b3880b523272
NOTE: The patch is largely untested.
Modifications:
- Update readme.org
- Remove geiser-company
- Move Company extensions to geiser-completion
Omissions:
- geiser-company--inhibit-autodoc has been removed. Eldoc handling
should be implemented in the frontend, not in the backend.
See for example:
https://github.com/minad/corfu/blob/04fbfce3d7e9c125a7fd22a34455a508247a522b/corfu.el#L1212
- The quickhelp-string action and geiser-company--docstring have been
removed. company-quickhelp can use `:company-doc-buffer` instead with
minimal overhead.
See:
https://github.com/company-mode/company-quickhelp/blob/3ca2708b4e5190205aca01d65fe1b391963a53f9/company-quickhelp.el#L138
- The automatic Company setup has been removed. Personally I am not a
fan of such auto configuration. It is better if completion is
configured consistently in the user configuration. You may want to
restore the auto configuration for backward compatibility. It depends
on your backward compatibility story. I am fine with rare breaking
changes from time to time.
- There is a cyclic dependency between geiser-edit/geiser-doc and
geiser-completion, which should be untangled.
Byte-compilation warnings fixed2022-04-23T14:49:05Zjaojao@gnu.org2022-04-23T14:49:05Zurn:sha1:77adf19d3812ecfd821d250f8bc1eb821a88ee92
And, actually, fixing bugs: the warnings weren't spurious.
autodoc: make do without dependending on elpa's eldoc2022-04-10T03:06:57Zjaojao@gnu.org2022-04-10T03:06:57Zurn:sha1:1300dd1a410a172588c529734a4fb1c8b58eaef1
Playing the trick of checking for eldoc-documentation-functions to
know wheter we're at a new enough version, and (hopefully) falling
back to the old implementation otherwise.
autodoc: new-style eldoc interface2022-04-10T02:45:17Zjaojao@gnu.org2022-04-10T02:45:17Zurn:sha1:dcbd8e81ac19ec808a4980ea99e7ee3f4f354c79
We remove by-now obsolete usage of eldoc, and depend on the elpa
package to ensure backwards compatibility.
A bit more tramp-friendliness2022-04-09T16:21:08Zjaojao@gnu.org2022-04-09T16:21:08Zurn:sha1:5b9532a571b28f1f82f0eaaecc1f7792473bdc6c
Fixes #45. Thanks to Brian Cully.
Shorten docstring that is over 80 characters wide2022-03-27T23:23:54ZJonas Bernoullijonas@bernoul.li2022-03-27T23:23:54Zurn:sha1:9507e81a075351d090fd1f4f708efd05d6470cba
The byte-compiler complained about it.
Support for #{...}# extended symbol syntax2022-03-24T00:51:33Zjaojao@gnu.org2022-03-24T00:51:33Zurn:sha1:cbfab92584072ba0e1c4119612a8438db61ecbf6
Should fix issue #41, possibly the oldest still standing! My thanks
and apologies to @ghost, wherever you are!
Missing version tag, and version bumped2022-03-23T23:48:42Zjaojao@gnu.org2022-03-23T23:48:42Zurn:sha1:bc0dde310492de733f9ec528d7aeddd57093d05e