<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser/elisp/geiser-capf.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>2025-09-22T22:30:26Z</updated>
<entry>
<title>...and, while we're at it, not printing spurious error messages</title>
<updated>2025-09-22T22:30:26Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@Mac.home</email>
</author>
<published>2025-09-22T22:30:26Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=6813afe4277491e91ee32ea30e9213b7b54fb868'/>
<id>urn:sha1:6813afe4277491e91ee32ea30e9213b7b54fb868</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: returning proper locations for company</title>
<updated>2025-09-22T22:02:36Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@Mac.home</email>
</author>
<published>2025-09-22T22:02:36Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=0a88bd27308e3ca3a62b6c933cdb97a4884237ea'/>
<id>urn:sha1:0a88bd27308e3ca3a62b6c933cdb97a4884237ea</id>
<content type='text'>
Should address issue #76. Thanks, Daniel.
</content>
</entry>
<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>expect completion-in-region functions to preserve current buffer</title>
<updated>2022-10-13T22:03:32Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-13T22:03:32Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=9a767e024da339aa12b0861473826384914ba010'/>
<id>urn:sha1:9a767e024da339aa12b0861473826384914ba010</id>
<content type='text'>
see discussion in issue #56
</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 completion-for-module</title>
<updated>2022-10-09T23:02:24Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-09T23:02:24Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=622e9becbe7a6706ab676cdbe8d78e9b2b4e1d1f'/>
<id>urn:sha1:622e9becbe7a6706ab676cdbe8d78e9b2b4e1d1f</id>
<content type='text'>
We were calling an undefined function... not too many people using the
functionality (or geiser at all :)).
</content>
</entry>
<entry>
<title>fix: don't override user's capfs (see issue #50)</title>
<updated>2022-08-20T19:30:49Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-08-20T19:30:49Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=ffff3931e104c73a0f332c9e181d11eebd81d816'/>
<id>urn:sha1:ffff3931e104c73a0f332c9e181d11eebd81d816</id>
<content type='text'>
</content>
</entry>
<entry>
<title>geiser-capf: new module to break cyclic dependencies</title>
<updated>2022-04-23T18:05:57Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-04-23T18:05:57Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=1b1fdd2be47fcbadab4b224266d30dee4484a4b0'/>
<id>urn:sha1:1b1fdd2be47fcbadab4b224266d30dee4484a4b0</id>
<content type='text'>
</content>
</entry>
</feed>
