<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser/elisp/geiser-custom.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-05T13:52:33Z</updated>
<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>
<entry>
<title>clarifications on geiser-custom--defcustom</title>
<updated>2024-07-05T13:28:31Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2024-07-05T13:28:31Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=2d3e4f9b3a83e4c42139e6b7b7ce84490c80d1eb'/>
<id>urn:sha1:2d3e4f9b3a83e4c42139e6b7b7ce84490c80d1eb</id>
<content type='text'>
In particular, removing a misleading FIXME comment that led to merge proposal
!22, and adding comments explaining why those changes would alter
geiser-reload's behaviour.
</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>geiser-custom: indent as declaration, lexical binding (Stefan Monnier)</title>
<updated>2022-01-27T23:52:20Z</updated>
<author>
<name>jao</name>
<email>jao@gnu.org</email>
</author>
<published>2022-01-27T23:52:20Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=8e582fa644b3ad0391a0c493ad6e2faaf677347a'/>
<id>urn:sha1:8e582fa644b3ad0391a0c493ad6e2faaf677347a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add doc-string to geiser-custom--defcustom</title>
<updated>2020-12-02T19:29:18Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-10-02T13:09:00Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=248d67f7632c191cf97955d346915736692bda72'/>
<id>urn:sha1:248d67f7632c191cf97955d346915736692bda72</id>
<content type='text'>
Also add a FIXME comment about how this macro isn't actually needed.
</content>
</entry>
<entry>
<title>Mark the beginning of code part of elisp libraries with Code: heading</title>
<updated>2020-03-27T20:38:45Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-02-25T13:32:18Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=3ceb31b71824e59e3f000edf7cb09ab86616d723'/>
<id>urn:sha1:3ceb31b71824e59e3f000edf7cb09ab86616d723</id>
<content type='text'>
It's the convention and by following it we make a big step towards
supporting outline navigation.

The convention doesn't say much about what parts of the code are
supposed to be part of that sections and what parts belong in a
subsequent section.  Here we put the `require' forms in this section
and maybe some setup code, that's a popular approach.

In most cases there was "" where we now insert "Code:".  They both
serve a similar purpose and we keep the former because some users
depend on that for navigation.  We even add this "" in libraries
where it previously was missing.

In some cases the permission statement was followed by a commentary,
which obviously does not belong in the "Code:" section.  In such cases
add the conventional "Commentary:" section.
</content>
</entry>
<entry>
<title>Remove Geiser faces from 'faces' custom group</title>
<updated>2015-09-23T16:17:07Z</updated>
<author>
<name>Alex Kost</name>
<email>alezost@gmail.com</email>
</author>
<published>2015-09-16T13:29:24Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=f8251641dc2048ef46e2089a8f2ccb119fe1f1f7'/>
<id>urn:sha1:f8251641dc2048ef46e2089a8f2ccb119fe1f1f7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add highlighting for geiser-custom--defcustom/defface</title>
<updated>2015-09-06T22:32:03Z</updated>
<author>
<name>Alex Kost</name>
<email>alezost@gmail.com</email>
</author>
<published>2015-09-06T18:55:36Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=bb3667a580d5c8dca7d88c0aaca6390c55978974'/>
<id>urn:sha1:bb3667a580d5c8dca7d88c0aaca6390c55978974</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Whitespace</title>
<updated>2012-10-11T02:17:35Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2012-10-11T02:17:35Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=b8630ca33b9abbcc5b39163d1df9180a66f1f998'/>
<id>urn:sha1:b8630ca33b9abbcc5b39163d1df9180a66f1f998</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Guile: geiser-guile-jump-on-debug-p, geiser-guile-show-debug-help-p</title>
<updated>2010-09-06T19:13:12Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2010-09-06T19:13:12Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=5f2d19e28bfe4860eaadd46010b29d34da8fc918'/>
<id>urn:sha1:5f2d19e28bfe4860eaadd46010b29d34da8fc918</id>
<content type='text'>
</content>
</entry>
</feed>
