summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-08-14Pushing the correct marker (fixes #279)Jose Antonio Ortega Ruiz
2019-08-07Add error reporting about missing symbols to geiser-edit.elLockywolf
Add (chibi filesystem) import to geiser.sld
2019-08-06Remove debug printing. Align par-style with geiser.Lockywolf
2019-08-06Add scheme subroutine to find files implementing modules to chibi.Lockywolf
Add a helper function make-location to chibi interface.
2019-06-24Fix: use default method implementationsJose Antonio Ortega Ruiz
See discussion in issue !256.
2019-06-13Introduce context-aware REPL send optionAaron Marks
This option allows for easier editing of expressions on the REPL without accidentally sending the input to the inferior Scheme. When turned on, the REPL behaves similarly to the Chez REPL.
2019-05-15Chicken 5 installation instructionsJose Antonio Ortega Ruiz
2019-05-15Alias for font-lock-ensure (should fix #274)Jose Antonio Ortega Ruiz
2019-02-10xref-push-marker-stack <- find-tag-marker-ringRyan Desfosses
2019-02-08Fix: off-by-one while fontifying REPL's outputJose Antonio Ortega Ruiz
2018-11-28Aaoron added to AUTHORSJose Antonio Ortega Ruiz
He really merits this mention for his great efforts to learn and finally find out the right thing!
2018-11-28Change behaviour of REPL output and highlightingAaron Marks
* Narrow font-lock syntax highlighting to only the active REPL input region. * Mark REPL output read-only. This can be changed via the option `geiser-repl-read-only-output-p`. * Mark REPL output with a user-definable face as `geiser-font-lock-repl-output`. Alternatively an option to syntax highlight REPL output is provided via the option `geiser-repl-highlight-output-p`. This applies scheme-mode syntax highlighting to any REPL output. Any additional hooks defined via scheme-mode-hook are also executed for highlighting this region. * Remove some unwanted TABs in source files.
2018-11-12Chicken 5 works with Geiser, many features removedDan Leslie
2018-11-12Readme and authors updatedJose Antonio Ortega Ruiz
2018-11-12Support 'quickhelp-string command for company-quickhelpAlexander Konstantinov
2018-11-12Make the geiser-company 'doc-buffer command work againAlexander Konstantinov
2018-06-26Not killing partial outputs when leaving the REPLJose Antonio Ortega Ruiz
Since this job is done in the process sentinel, the clean up is also triggered when the Scheme process exits unexpectedly, deleting any traces the dying guy might have left. I added a flag to control the behaviour, but upon reflection the old behaviour seems wrong and i've defaulted to the new one. This one should fix #251.
2018-06-11Documentation warningJose Antonio Ortega Ruiz
2018-06-11Making README a productJose Antonio Ortega Ruiz
Generated by simply copying README.org. The trick of making README a symbolic link was, well, a trick, and seems to confuse poor Gitlab.
2018-06-10Moving to GitlabJose Antonio Ortega Ruiz
Probably not a totally smart move, since sooner or later gitlab's going to fall as github did (for a fruity company would be my bet). But oh well, at least we can export a CSV of the issues!
2018-04-14Adding proper entries to load-path (fixes #246)Jose Antonio Ortega Ruiz
And we also take the chance to let add-to-list do its job of not adding duplicates.
2018-04-02Those lines are not table headersJose Antonio Ortega Ruiz
2018-04-02I don't know why github's org parser is playing games with meJose Antonio Ortega Ruiz
2018-04-02More README tweaksJose Antonio Ortega Ruiz
2018-04-02More README tweaksJose Antonio Ortega Ruiz
2018-04-02Trying harder to use proper org markup in READMEJose Antonio Ortega Ruiz
and make github happier in the process (cf. github issue #243)
2018-04-02Trying to use proper org markup in READMEJose Antonio Ortega Ruiz
And thus avoiding having to generate markdown (cf. github issue #243)
2018-03-19A prefix for geiser-compile-current-buffer to restart it allJose Antonio Ortega Ruiz
Okay, i must confess it's sometimes handy to restart the REPL before compiling a file (the proverbial clean slate and all). And we already have geiser-restart-repl, so combining the two things when C-u happens was not really difficult.
2018-03-14Simpler navigation bar in websiteJose Antonio Ortega Ruiz
Savannah downloads is often broken, and the news page doesn't really add any value.
2018-03-14TypoJose Antonio Ortega Ruiz
2018-03-14Release 0.100.10Jose Antonio Ortega Ruiz
2018-02-03Emacs 24 compatibility: completion-table-dynamicJose Antonio Ortega Ruiz
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.
2018-01-30versions bumped (and hope for a february release)Jose Antonio Ortega Ruiz
2018-01-29Fix for module/identifier completion in minibufferJose Antonio Ortega Ruiz
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.
2018-01-26New HACKING fileJose Antonio Ortega Ruiz
2017-11-22Theoretically unnecessary save-excursionJose Antonio Ortega Ruiz
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.
2017-11-18Fix typo in installation's commandZiyi Yan
`install-package` -> `package-install`
2017-09-29make a link to the subheading in the previous commit in parens.texiGeorge D. Plymale II
2017-09-29add subheading to repl.texi to caution about completion & the REPLGeorge D. Plymale II
as per the discussion at: https://github.com/jaor/geiser/issues/183
2017-09-25Do not set geiser last-prompt-end beyond of point-maxMario Rodas
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-08-04Improve LICENSE textJonas Bernoulli
This is still the same license, but now it is closer to the text expected by tools that automatically extract license information.
2017-07-04replace broken autocomplete-mode linkAndrew Sackville-West
used Emacs Wiki link since it links on to the code and is likely to be kept relatively up-to-date
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).