summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-07-02Fix for the fix for broken linksJose Antonio Ortega Ruiz
Actually, programming-musings.org is no longer a domain i pay for, and the "canonical" reference to my blog post is in jaortega.wordpress.com.
2017-07-01fix broken links to incremental REPL referencesAndrew Sackville-West
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-26repl.texi: Put @altr on its own line so "Other" is not omittedJames C. De Ricco
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-02-01A note on dir-locals and load-path variablesJose Antonio Ortega Ruiz
With that in the documentation, i'd taken less time to remember the very existence of geiser-guile-load-path, and the fact that paths are added also to the compiled load path... but then i guess it's nice to re-read my code once in a while.
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-26Make guile's load-file happier with ~ abrevsJose Antonio Ortega Ruiz
An attempt to address #194.
2016-11-09Same as before, but for geiser-mit-source-directory: it's 'directoryJose Antonio Ortega Ruiz
2016-11-09Same as before, but for geiser-mit-source-directory: it's 'directoryJose Antonio Ortega Ruiz
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-24Missing chibi and chez support filesJose Antonio Ortega Ruiz
Should fix #188, and i'm not generating a new version for this unless some distribution maintainer is asking.
2016-10-10chez, chibi and mit belong into geiser-active-implementationsJose Antonio Ortega Ruiz
At least by default.
2016-10-06Release 0.90.9Jose Antonio Ortega Ruiz
2016-10-02racket: indentation for 'shared'Jose Antonio Ortega Ruiz
2016-09-30gitignoring mit scheme's compilation artifactsJose Antonio Ortega Ruiz
2016-09-30Use (car (process-lines ...)) instead of (shell-command ...)Jordan Brown
`shell-command` assumes Bourne-shell-compatible quoting, which doesn't work when the user isn't using a Bourne-compatible shell. Instead of futzing about with quoting, we can just use `process-lines` to execute a process and pass it arguments directly.
2016-09-21Expand socket file name for 'geiser-connect-local'Alex Kost
2016-09-17Allows Chicken to limit the number of symbols provided to Geiserdleslie
- Also cleaned up the namespace a little.
2016-09-06Add link to project homepageChunyang Xu
C-h P (`display-package') can make use of it.
2016-09-06Fix link to melpa-stableChunyang Xu
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-10Adds required modules to binary parametersDan Leslie
-This causes chicken to fail to run if it cannot find the required modules for Geiser; and will tell the user that the module is missing.
2016-08-10Disable aggressive prefix assumptionDan Leslie
This was causing significant typing delay with little to no benefit. Disabled until a better solution can be found.
2016-08-10Remove compilation of chicken moduleDan Leslie
This was causing confusion and bug reports on a semi-regular basis. Disable it for now until a better solution is made.
2016-08-10Add chez, mit, and chibi to autoloadDan Leslie
2016-08-10Minor typoDan Leslie
2016-07-26README as an org fileJose Antonio Ortega Ruiz
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-11Lower minimum MIT Scheme versionFice T
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.