summaryrefslogtreecommitdiff
path: root/elisp
AgeCommit message (Collapse)Author
2017-08-28WhitespaceJose Antonio Ortega Ruiz
2017-08-28Add geiser-mode-eval-to-buffer-transformerChaos Eternal
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 (< (+ 1 p) l)) (format "\n#| %s%s\n |#" estring x) (format ";;=> %s%s" estring x)))))
2017-04-11Preserve the position of (point) after evalingDiogo F. S. Ramos
After evaling the last expression, if not inserting its value into buffer, leave (point) at its original position.
2017-04-11Eval last expression even after a comment charDiogo F. S. Ramos
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.
2017-03-21Don't assign the (field t) property to old REPL inputsJames C. De Ricco
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).
2017-01-27bug fix: error message get displayedChaos Eternal
2017-01-17Not inserting a trailing \n when eval prefix is emptyJose Antonio Ortega Ruiz
And, on reflection, it's better we do the same thing with the ERROR insertion...
2017-01-17Not inserting an additional \n when eval prefix is emptyJose Antonio Ortega Ruiz
2017-01-13Make eval-last-sexp-to-buffer customizableChaos Eternal
2016-12-03Bug fix: expanding file name at the right timeJose Antonio Ortega Ruiz
We were expanding the path of files to be loaded at the wrong place in the wrong way. This should be better and address bug #196.
2016-11-26fix malformed argument lists.Peter Wang
Emacs trunk does not support arguments list like (lambda (&rest) nil) anymore, which breaks geiser and errors with "Invalid function: "
2016-11-09It's file, not filename (should fix #190)Jose Antonio Ortega Ruiz
2016-10-24Missing geiser-{chibi,chez}.el in distJose Antonio Ortega Ruiz
2016-10-10chez, chibi and mit belong into geiser-active-implementationsJose Antonio Ortega Ruiz
At least by default.
2016-09-21Expand socket file name for 'geiser-connect-local'Alex Kost
2016-09-06Add link to project homepageChunyang Xu
C-h P (`display-package') can make use of it.
2016-08-29Pacify byte-compiler a bitFice T
2016-08-26Not signalling errors for company-mode completionsJose Antonio Ortega Ruiz
... so that we don't interfere with other active backends, and following the same policy as in the rest of company-mode geiser methods. See also the discussion in github's #173.
2016-08-24Making autodoc failures silentJose Antonio Ortega Ruiz
As requested in github issue #173. Seems it's confusing people, which is exactly the problem it was originally trying to avoid!
2016-08-10Add chez, mit, and chibi to autoloadDan Leslie
2016-06-17Be in good terms with haskell-modeJose Antonio Ortega Ruiz
Avoid redefining font-lock-ensure, so that haskell-mode doesn't get mad at us. Should close github's #164.
2016-06-13(end-of-line 0) > (forward-line -1) (end-of-line)Jose Antonio Ortega Ruiz
2016-06-13Fixing again, sorry about thatJose Antonio Ortega Ruiz
2016-06-13A few byte-compilation warnings silencedJose Antonio Ortega Ruiz
2016-06-12New key bindings: C-c C-c, C-c C-lJose Antonio Ortega Ruiz
2016-06-12Fix for the by now famous syntax keywords patchJose Antonio Ortega Ruiz
2016-06-12New commands geiser-repl-{previous,next}-promptJose Antonio Ortega Ruiz
When using a prompt regexp, comint's version of these commands misbehave (they try to reuse forward-paragraph, and that's not quite it), so we're implemeting our own here in a very straightforward way. We also bind the usual C-c C-p and C-c C-n to them. It only remains to b seen whether advising the original ones is worth the trouble.
2016-06-12Real fix fontification on scheme switchJose Antonio Ortega Ruiz
2016-06-12REPLs not started by the font-lock bufferJose Antonio Ortega Ruiz
This one should fix github's issue #132. There's still the glitch that scheme strings are fontified without taking into account extra keywords.
2016-06-12Removing stale keywords when switching to another schemeJose Antonio Ortega Ruiz
Addresses github's #158, and its implementation is really easy (kudos to fice-t, also for telling me about bound-and-true-p).
2016-06-12Registering *global* font-lock keywords in REPLs at the right timeJose Antonio Ortega Ruiz
We were adding only the scheme-specific ones.
2016-06-11Registering font-lock keywords in REPLs at the right timeJose Antonio Ortega Ruiz
We were doing it before the buffer's implementation, and the implementation-specific keywords were not found. Should fix github's issue #159.
2016-06-11Cleanups to the show/jump debug buffer messJose Antonio Ortega Ruiz
Let's see if i finally got this right...
2016-05-29Fixes for geiser-debug-jump-to-debug-p and geiser-debug-show-debug-pJose Antonio Ortega Ruiz
I wonder if this has ever worked fine: geiser-debug--display-retort was a little mess. It should be a bit better now, but Guile is still displaying funny messages.
2016-04-30Fix REPL restart if REPL is aliveAlex Kost
2016-04-30Add chez to Makefile, add autoloads for chezPeter
2016-04-30Add chez to Makefile, add autoloads for chezPeter
2016-04-26Add preliminary support for MIT/GNU Scheme.Peter
2016-04-23Define 'geiser-xref-mode' with 'define-derived-mode'Alex Kost
2016-04-23Define 'geiser-debug-mode' with 'define-derived-mode'Alex Kost
2016-04-23Define 'geiser-doc-mode' with 'define-derived-mode'Alex Kost
2016-04-23Initialize 'geiser-doc-mode-map' inside defvarAlex Kost
2016-04-23Fix indentation of named 'match-let'Alex Kost
This fixes a regression introduced by commit 424553e017718c54e219212b27a32b341ec6bd28.
2016-04-20Do not use 'geiser-xref--with-buffer' before it is definedAlex Kost
This is a fix similar to the one made in commit 8e75455dfbd46355d777c26366e7ccfcb59ace20.
2016-04-10Use assq instead of assoc in request and connection wrappersAlex Kost
2016-04-10Remove double call in 'geiser-con--connection-add-request'Alex Kost
Avoid calling 'geiser-con--request-string' twice by wrapping it into 'let'.
2016-04-07Fix REPL reconnectingAlex Kost
This fixes 2 issues: 1. Reconnecting to a remote process prompts for host/port, although it is not needed. 2. 'geiser-connect' should be used only if 'geiser-repl--address' is a host/port pair. When it is a socket file name, 'geiser-connect-local' should be used.
2016-01-07Behave nicely with other company backendsDan Leslie
company-backends should not be overridden by modes, as users may have additional backends that they wish to use. The appropriate behaviour is to add your backend to the company-backends list. Also removed the overriding of what ought to be user-controlled variables.
2015-12-27Avoiding uses of geiser-doc--with-buffer before its definitionJose Antonio Ortega Ruiz
As patiently pointed out by Alex Kost in the discussion of issue #121, using the macro defined by the geiser-popup--define macro before its actual definition causes problems when geiser is loaded after compilation. Thanks again, Alex and Federico.
2015-12-14Fix geiser-connect-local for non-interactive useAlex Kost
Move prompting for a socket file name to the interactive form.