<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser/elisp/geiser-autodoc.el, branch 0.33</title>
<subtitle>emacs and scheme talk to each other</subtitle>
<id>https://jao.io/cgit/geiser/atom?h=0.33</id>
<link rel='self' href='https://jao.io/cgit/geiser/atom?h=0.33'/>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/'/>
<updated>2024-07-06T15:37:23Z</updated>
<entry>
<title>Cleanup library headers</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-07-14T12:33:38Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=de52f0e36f1709181c1ce4e787d79208fa2cb870'/>
<id>urn:sha1:de52f0e36f1709181c1ce4e787d79208fa2cb870</id>
<content type='text'>
- 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.
</content>
</entry>
<entry>
<title>Fix typos</title>
<updated>2023-07-14T00:38:02Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2023-07-14T00:38:02Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=dc25a8868f39c9f572b051e9a7ea2b68f65aa2b2'/>
<id>urn:sha1:dc25a8868f39c9f572b051e9a7ea2b68f65aa2b2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Take the byte-compilers advice into account</title>
<updated>2022-12-05T14:17:55Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-12-05T14:17:55Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=a60efa80cdb8c72dacb1e16729a801206a4e80bf'/>
<id>urn:sha1:a60efa80cdb8c72dacb1e16729a801206a4e80bf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>more tweaks to regexp signature finding</title>
<updated>2022-10-21T00:26:04Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-21T00:26:04Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=2174f90b64343c1af76c8e5469d5e4b69d709c08'/>
<id>urn:sha1:2174f90b64343c1af76c8e5469d5e4b69d709c08</id>
<content type='text'>
and its use in autodoc (for instance, skip it when in the REPL).
</content>
</entry>
<entry>
<title>fix for autodoc, ahem, extension</title>
<updated>2022-10-16T03:14:37Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-16T03:14:37Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=8637d72db828328ea645466036878820ec92d183'/>
<id>urn:sha1:8637d72db828328ea645466036878820ec92d183</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fallback autodoc inferred via cheap regexps</title>
<updated>2022-10-16T01:59:54Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-16T01:59:54Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=c437b1eca906f9c06eb5acef49f84bc4a87d2b8b'/>
<id>urn:sha1:c437b1eca906f9c06eb5acef49f84bc4a87d2b8b</id>
<content type='text'>
same code that finds putative definitions, with all its caveats
</content>
</entry>
<entry>
<title>autodoc: correctly display docsigs for in-region completions (#56)</title>
<updated>2022-10-13T01:44:59Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-13T01:44:59Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=727d2dfe988943c277804d87ac9cd40f2ddc65e0'/>
<id>urn:sha1:727d2dfe988943c277804d87ac9cd40f2ddc65e0</id>
<content type='text'>
we were doing it really wrong: first, by not setting the evaluation
environment when things are computed outside the original buffer (the
completion in region case for consult and the likes, where the current buffer
is the minibuffer) and, to add insult to injury, by not waiting for a response
from the scheme side!

actually waiting can make things a tad laggy when the scheme is not as fast
as, say, chez and there are lots of completions (if one uses
completion-in-region; for pop ups like company it's fine), so i've also added
a flag, geiser-autodoc-use-docsig, to turn the functionality off.
</content>
</entry>
<entry>
<title>Fix for autodoc in geiser-capf--company-docsig and beyond</title>
<updated>2022-09-17T16:59:44Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-09-17T16:59:44Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=486c39cfbdf1789fe493535b7e0ae72ff518e53e'/>
<id>urn:sha1:486c39cfbdf1789fe493535b7e0ae72ff518e53e</id>
<content type='text'>
Thanks to Panagiotis Vlantis, see issue #54
</content>
</entry>
<entry>
<title>Byte-compilation warnings fixed</title>
<updated>2022-04-23T14:49:05Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-04-23T14:49:05Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=77adf19d3812ecfd821d250f8bc1eb821a88ee92'/>
<id>urn:sha1:77adf19d3812ecfd821d250f8bc1eb821a88ee92</id>
<content type='text'>
And, actually, fixing bugs: the warnings weren't spurious.
</content>
</entry>
<entry>
<title>autodoc: make do without dependending on elpa's eldoc</title>
<updated>2022-04-10T03:06:57Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-04-10T03:06:57Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=1300dd1a410a172588c529734a4fb1c8b58eaef1'/>
<id>urn:sha1:1300dd1a410a172588c529734a4fb1c8b58eaef1</id>
<content type='text'>
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.
</content>
</entry>
</feed>
