<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser/elisp/geiser-edit.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:02:36Z</updated>
<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>Buttons live in their own namespace</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-08-12T13:07:18Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=f74612686b468069849ab36d1c49229312f3434e'/>
<id>urn:sha1:f74612686b468069849ab36d1c49229312f3434e</id>
<content type='text'>
`geiser-doc--xbutton' will be tackled in the next commit.
</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>geiser-edit: new customization group</title>
<updated>2024-02-08T00:26:36Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2024-02-08T00:26:36Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=4e64934bd2ae7c6f0e4acb9f2ed017844c187223'/>
<id>urn:sha1:4e64934bd2ae7c6f0e4acb9f2ed017844c187223</id>
<content type='text'>
Fixes issue #20
</content>
</entry>
<entry>
<title>edit: Add geiser-insert-actual-lambda.</title>
<updated>2024-01-15T18:41:38Z</updated>
<author>
<name>Tomas Volf</name>
<email>~@wolfsden.cz</email>
</author>
<published>2024-01-13T13:18:04Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=cfe14bf11096ded649b57e2532302321044d51c6'/>
<id>urn:sha1:cfe14bf11096ded649b57e2532302321044d51c6</id>
<content type='text'>
Some projects use λ, some use lambda, and it is convenient to be able to use the
same mapping engraved into muscle memory for both.  Therefore this commit adds a
new variable that allow geiser-insert-lambda to do both, depending on the value.

* elisp/geiser-edit.el (geiser-insert-actual-lambda): New variable.
(geiser-insert-lambda): Respect it.
</content>
</entry>
<entry>
<title>fix: better error message for symbol not found on M-.</title>
<updated>2023-10-01T19:32:31Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2023-10-01T19:32:31Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=58bd510da5d09d9de52f4a6e60882b35445ca17a'/>
<id>urn:sha1:58bd510da5d09d9de52f4a6e60882b35445ca17a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Address byte-compiler warning</title>
<updated>2023-05-03T10:44:42Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2023-05-03T10:44:42Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=83305e6bb5f13d68f8e31d457605b02d2a10c014'/>
<id>urn:sha1:83305e6bb5f13d68f8e31d457605b02d2a10c014</id>
<content type='text'>
Warning: ‘backward-delete-char’ is for interactive use only;
use ‘delete-char’ instead.
</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>requiring subr-x at compile time for older emacsen</title>
<updated>2022-11-01T16:22:34Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-11-01T16:22:34Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=dbde6d2b446b41bc309da33aa69034c63f8294a5'/>
<id>urn:sha1:dbde6d2b446b41bc309da33aa69034c63f8294a5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>debugging commands up to the specific scheme implementation</title>
<updated>2022-10-22T22:55:53Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-10-22T22:55:53Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=fd58d38118e2c409db524ccc8ff213e8d98a43bf'/>
<id>urn:sha1:fd58d38118e2c409db524ccc8ff213e8d98a43bf</id>
<content type='text'>
the half backed attempt at standardising guile's model won't work well with
other schemes, and it's not really well thought-out anyway: let's guile do its
thing, and we'll see what we can do in chez.
</content>
</entry>
</feed>
