<feed xmlns='http://www.w3.org/2005/Atom'>
<title>geiser/elisp, branch 0.10</title>
<subtitle>emacs and scheme talk to each other</subtitle>
<id>https://jao.io/cgit/geiser/atom?h=0.10</id>
<link rel='self' href='https://jao.io/cgit/geiser/atom?h=0.10'/>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/'/>
<updated>2018-02-03T02:25:44Z</updated>
<entry>
<title>Emacs 24 compatibility: completion-table-dynamic</title>
<updated>2018-02-03T02:25:44Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2018-02-03T02:25:44Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=2c9eb408702866f8d57e0e3f5b2eace9e70f6b63'/>
<id>urn:sha1:2c9eb408702866f8d57e0e3f5b2eace9e70f6b63</id>
<content type='text'>
Looks like the arity of that function changed at some point between 24
and 25.  It also looks like people still use emacs 24 (see issue #236),
so here we go.
</content>
</entry>
<entry>
<title>Fix for module/identifier completion in minibuffer</title>
<updated>2018-01-29T02:21:13Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2018-01-29T02:21:13Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=2af5b24c97a271c243d8fddbc6b7bc97544c29da'/>
<id>urn:sha1:2af5b24c97a271c243d8fddbc6b7bc97544c29da</id>
<content type='text'>
When constructing the completion table for minibuffer prompts via
`completion-table-dynamic', we were forgetting to tell emacs to
perform the completion lookup with the original (scheme) buffer as its
current buffer.  As a result, the actual completion function wasn't
able to find the REPL connection and everything when down in flames
with an exception.
</content>
</entry>
<entry>
<title>Theoretically unnecessary save-excursion</title>
<updated>2017-11-22T03:01:45Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2017-11-22T03:01:45Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=0be9384a6812343b82a01c1af3a45b677a0a12be'/>
<id>urn:sha1:0be9384a6812343b82a01c1af3a45b677a0a12be</id>
<content type='text'>
For some reason, one of our users is experiencing point jumps when
calling `geiser-set-scheme'.  A save-excursion is all that's needed,
even though it *shouldn't* be needed in the first place.
</content>
</entry>
<entry>
<title>Do not set geiser last-prompt-end beyond of point-max</title>
<updated>2017-09-25T22:57:47Z</updated>
<author>
<name>Mario Rodas</name>
<email>marsam@users.noreply.github.com</email>
</author>
<published>2017-09-23T16:20:38Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=9291e76e2b783fb7b4c91c02dcf596e23221f65c'/>
<id>urn:sha1:9291e76e2b783fb7b4c91c02dcf596e23221f65c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Whitespace</title>
<updated>2017-08-28T00:55:07Z</updated>
<author>
<name>Jose Antonio Ortega Ruiz</name>
<email>jao@gnu.org</email>
</author>
<published>2017-08-28T00:53:22Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=cbdb8c928957c140f9a3c4154db21df9c4341613'/>
<id>urn:sha1:cbdb8c928957c140f9a3c4154db21df9c4341613</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add geiser-mode-eval-to-buffer-transformer</title>
<updated>2017-08-28T00:54:04Z</updated>
<author>
<name>Chaos Eternal</name>
<email>chaos@shlug.org</email>
</author>
<published>2017-08-20T14:23:38Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=e1b9f87e535a43d04a5572bed820f029213c5b13'/>
<id>urn:sha1:e1b9f87e535a43d04a5572bed820f029213c5b13</id>
<content type='text'>
geiser-mode-eval-to-buffer-transformer will take 2 argments:
errstring and result
when eval-to-buffer, the result will be transformed by this procedure
e.g.
(setq geiser-mode-eval-to-buffer-transformer
      (lambda (estring x)
	(let ((l (length x))
	      (p (seq-position x ?\n)))
	  (if (and p (&lt; (+ 1 p) l))
	      (format "\n#| %s%s\n  |#" estring x)
	    (format ";;=&gt; %s%s" estring x)))))
</content>
</entry>
<entry>
<title>Preserve the position of (point) after evaling</title>
<updated>2017-04-11T17:21:30Z</updated>
<author>
<name>Diogo F. S. Ramos</name>
<email>dfsr@riseup.net</email>
</author>
<published>2017-04-11T15:42:24Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=bffaaae6d2e752d2e6844e7f590945f4d54ea31a'/>
<id>urn:sha1:bffaaae6d2e752d2e6844e7f590945f4d54ea31a</id>
<content type='text'>
After evaling the last expression, if not inserting its value into
buffer, leave (point) at its original position.
</content>
</entry>
<entry>
<title>Eval last expression even after a comment char</title>
<updated>2017-04-11T17:21:07Z</updated>
<author>
<name>Diogo F. S. Ramos</name>
<email>dfsr@riseup.net</email>
</author>
<published>2017-04-11T15:42:23Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=2834cd900779ad8966bc997f1a5c65122bbe3a63'/>
<id>urn:sha1:2834cd900779ad8966bc997f1a5c65122bbe3a63</id>
<content type='text'>
Scan for beginning and end of a sexp, instead of using (point) as the
end.

Previously, if (point) was after a comment character, the REPL would
freeze.
</content>
</entry>
<entry>
<title>Don't assign the (field t) property to old REPL inputs</title>
<updated>2017-03-21T05:15:02Z</updated>
<author>
<name>James C. De Ricco</name>
<email>jamescdericco@gmail.com</email>
</author>
<published>2017-03-21T04:57:24Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=c5e141e892a9b4b4a339ee647f355fd025c9f9ab'/>
<id>urn:sha1:c5e141e892a9b4b4a339ee647f355fd025c9f9ab</id>
<content type='text'>
Previously, Geiser added a (field t) property to inputs before adding
them to the REPL history so it can determine what characters in the
buffer belong to old input and yank it when a user pressed
enter (geiser-repl--maybe-send) on it. When users recalled an old
input with "M-p" (comint-previous-matching-input-from-input), the old
input with its (field t) property were inserted after the current
prompt. Since old inputs were not "front-sticky," when point was just
after the current prompt but before the characters of the old input,
Emacs considered point to be outside of the (field t) field; this
prevented users from using some movement commands such as forward-word
to move point into the old input text. Furthermore, when users
inserted text before the old input or yanked other old inputs
afterwards, this new text did not have the field property and so Emacs
restricted point movement to and from the old text with the (field t)
field.

This resolves the issue by not adding the (field t) property to old
inputs and instead leverages comint's ability to assign the output
field to all non-input (by setting comint-use-prompt-regexp to
nil). It should resolve the issue reported in "[Geiser-users] Problem
with prompt at history item" by Hamish Ivey-Law
(https://lists.nongnu.org/archive/html/geiser-users/2014-12/msg00001.html).
</content>
</entry>
<entry>
<title>bug fix: error message get displayed</title>
<updated>2017-01-27T02:40:09Z</updated>
<author>
<name>Chaos Eternal</name>
<email>chaos@shlug.org</email>
</author>
<published>2017-01-27T02:40:09Z</published>
<link rel='alternate' type='text/html' href='https://jao.io/cgit/geiser/commit/?id=7be1dd2a46d2d025d779a156236240d3b737862f'/>
<id>urn:sha1:7be1dd2a46d2d025d779a156236240d3b737862f</id>
<content type='text'>
</content>
</entry>
</feed>
