summaryrefslogtreecommitdiff
path: root/elisp
AgeCommit message (Collapse)Author
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.
2015-12-05Removed changes to geiser-connectionDan Leslie
2015-12-05Fixes for Literals, Errors and ModulesDan Leslie
If literals were present chicken wouldn't provide any autodocumentation due to an error. Module evaluation was failing due to poor input. Chicken's Error output was failing to parse - Filter out all non-symbols from the autodoc set - Properly escape module names - Add "Error" to the set of accepted error prefixes
2015-10-13Oops: font-lock-ensure is from the futureJose Antonio Ortega Ruiz
Should fix #105
2015-10-12So font-lock-fontify-buffer is for interactive useJose Antonio Ortega Ruiz
Fixed by using font-lock-ensure instead
2015-10-12Keeping the elisp compiler happyJose Antonio Ortega Ruiz
Mainly by reordering definitions so that functions are not used before defined. There are a couple of places where the compiler and I disagree (it complains withing eval-after-load), and a valid complain about functions defined via geiser-popup--define that should be addressed).
2015-10-03Add missing highlighting for 'syntax-case'Alex Kost
2015-10-03Add highlighting/indentation for testsAlex Kost
API for test suites is defined by SRFI-64.
2015-10-03Add highlighting/indentation for exceptionsAlex Kost
Exceptions are defined by R6RS, SRFI-18 and SRFI-34.
2015-09-27Clean up indentation rulesAlex Kost
Move general indentation rules to "geiser-syntax".
2015-09-27Add general font-lock keywords for all implementationsAlex Kost
Move general RNRS/SRFI keywords from "geiser-chicken" to "geiser-syntax".
2015-09-27Add 'geiser-syntax--simple-keywords'Alex Kost
Use this function instead of repeating the same code in each implementation.
2015-09-23Remove Geiser faces from 'faces' custom groupAlex Kost
2015-09-16Add 'geiser-repl-buffer-name-function' variableAlex Kost
2015-09-10Speeding up debugger check (addresses #64)Jose Antonio Ortega Ruiz
Soooo, the long delay experienced when evaluating long string lists in Guile had nothing to do with the time took by emacs to read the response from the scheme process; that process is always a breeze, no matter or its format or number of newlines. The delay was provoked by an innocent looking function that scans the received string (which includes a prompt at the end as an EOT marker) to check whether Guile (or any other scheme) has just entered the debugger (that's done inside `geiser-con--connection-update-debugging`). For some reason, `string-match` on that kind of string using Guile's regexp for a debug prompt takes forever. Instead of trying to optimize the regular expression, i've just applied it to the *second* line of the received string, which is the one that contains the response's prompt.
2015-09-10Fix for geiser-connect-localJose Antonio Ortega Ruiz
This one should address #79. I'm very surprised this ever worked!
2015-09-10Moving implementation loading to geiser-repl (#82)Jose Antonio Ortega Ruiz
That way we avoid circularities in the load graph, always a good thing.
2015-09-10Redundant provide in define-geiser-implementationJose Antonio Ortega Ruiz
This is gone now, since we're diligent enough to always end our impl definitions with an explicit provide form. See PR #87 for a bit of discussion.
2015-09-09WhitespaceJose Antonio Ortega Ruiz
2015-09-09Autoload geiser-connect-local as wellChristoph Egger
2015-09-08Ensuring switch-to-geiser asks for an implementationJose Antonio Ortega Ruiz
Should fix issue #85
2015-09-07Add highlighting for geiser-custom--defcustom/deffaceAlex Kost