<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser, branch 0.31.1</title>
<subtitle>emacs and scheme talk to each other</subtitle>
<id>https://jao.io/cgit/geiser/atom?h=0.31.1</id>
<link rel='self' href='https://jao.io/cgit/geiser/atom?h=0.31.1'/>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/'/>
<updated>2024-09-01T19:54:11Z</updated>
<entry>
<title>version bump</title>
<updated>2024-09-01T19:54:11Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2024-09-01T19:54:11Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=c034c129cfa7442881f13ae146c87785b367cff5'/>
<id>urn:sha1:c034c129cfa7442881f13ae146c87785b367cff5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fixes for new button types handling</title>
<updated>2024-07-26T12:17:56Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2024-07-26T12:17:56Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=3b02581c8422d416d1d4dc3168db5cf7b0ef16fc'/>
<id>urn:sha1:3b02581c8422d416d1d4dc3168db5cf7b0ef16fc</id>
<content type='text'>
Fixes issue #68.
</content>
</entry>
<entry>
<title>Replace a button type with two new types</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2024-02-07T23:09:22Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=a81969a5271f155d2d1e389ccbe47e1c7ec36ae7'/>
<id>urn:sha1:a81969a5271f155d2d1e389ccbe47e1c7ec36ae7</id>
<content type='text'>
That results in less code and less confusing indirection.
</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>Define autoloads how that is normally done</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-07-14T14:06:12Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=67f727855895050aca3bcf37066e804dc8f307de'/>
<id>urn:sha1:67f727855895050aca3bcf37066e804dc8f307de</id>
<content type='text'>
- Avoid defining autoload definitions in a central location.
  Instead add autoload cookies to the forms/definitions that should
  be autoloaded, in the locations where the actual definitions are
  located.

  - Do this for `geiser-mode', `turn-on-geiser-mode',
    `geiser-mode--maybe-activate' (including adding that to
    `scheme-mode-hook'), `geiser', `geiser-connect',
    `geiser-connect-local' and `geiser-repl-switch'.

  - Also do this for `run-geiser', even though it is only an obsolete
    function alias for `geiser', which might make it desirable to drop
    the autoload altogether.

  Some unusual autoload definitions remain in "geiser.el", see below.

- One issue with defining autoloads in a central location is that it
  is easy to forget to remove such autoloads when the real definition
  is removed.

  No longer autoload `geiser-version' because since [1: 847d2ad]
  there no longer exists a proper definition of that function.

- No longer autoload `geiser-unload', `geiser-reload' and
  `turn-off-geiser-mode', because they are only useful if Geiser has
  already been loaded, at which point any autoloaded definitions are
  no longer relevant.

However,

- Keep autoloading `geiser-activate-implementation' and
  `geiser-implementation-extension', even though I doubt that this
  is actually useful.

- Keep using `custom-add-load' to specify dependencies of Custom
  groups and keep autoloading that.  I don't know if this is actually
  necessary, and while it seems really weird, it might served a legit
  purpose, that I am not aware of.

1: 2020-07-19 847d2ad4c6da462c26c50af1ef7d9cd697f3a5d2
   scheme and autotools removals
</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>Define geiser--feature-list as a variable</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-07-14T14:20:48Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=9197acbdbde392fc53ad0f2be2cef83e452f1d28'/>
<id>urn:sha1:9197acbdbde392fc53ad0f2be2cef83e452f1d28</id>
<content type='text'>
Defining it as a macro, as it was done from the start, is just
weird.
</content>
</entry>
<entry>
<title>geiser-elisp-dir: Fallback to buffer-file-name</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-07-14T12:27:28Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=b57fdc8fde91734b34b7ad1c2f1a06b46a1f5822'/>
<id>urn:sha1:b57fdc8fde91734b34b7ad1c2f1a06b46a1f5822</id>
<content type='text'>
This makes it possible to `eval-buffer' the buffer defining this
constant.  Not that doing so makes all that much sense, but I tried
doing it before reading its content, because generally speaking that
is a sensible thing to do, at least for someone working on the code.
</content>
</entry>
<entry>
<title>Define ring-member immediately if necessary</title>
<updated>2024-07-06T15:37:23Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2022-07-14T12:22:44Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=e3dd43e247591e588f530ed15867766aa9cc9482'/>
<id>urn:sha1:e3dd43e247591e588f530ed15867766aa9cc9482</id>
<content type='text'>
Right above the changed lines we require `ring'.  It is therefore not
necessary to delay evaluation until `ring' has been loaded; we know it
has already been loaded.
</content>
</entry>
<entry>
<title>further clarifications re geiser-custom</title>
<updated>2024-07-05T13:52:33Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2024-07-05T13:52:33Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=410a3a50d724c0aaf8d209d6a620976828854881'/>
<id>urn:sha1:410a3a50d724c0aaf8d209d6a620976828854881</id>
<content type='text'>
A note on why we won't use the mapatom trick to make geiser-custom--defcustom
obsolete while still preserving geiser-reload functionality (cf. !22).
</content>
</entry>
</feed>
