summaryrefslogtreecommitdiff
path: root/elisp
AgeCommit message (Collapse)Author
2020-03-27Mark the beginning of code part of elisp libraries with Code: headingJonas Bernoulli
It's the convention and by following it we make a big step towards supporting outline navigation. The convention doesn't say much about what parts of the code are supposed to be part of that sections and what parts belong in a subsequent section. Here we put the `require' forms in this section and maybe some setup code, that's a popular approach. In most cases there was " " where we now insert "Code:". They both serve a similar purpose and we keep the former because some users depend on that for navigation. We even add this " " in libraries where it previously was missing. In some cases the permission statement was followed by a commentary, which obviously does not belong in the "Code:" section. In such cases add the conventional "Commentary:" section.
2020-03-27Begin the summary lines of all elisp libraries with three semicolonsJonas Bernoulli
It's the convention and by following it we make a big step towards supporting outline navigation.
2020-03-16define-geiser-implementation - un-unquote load-file-namespellcard199
2020-02-25Fix for misspelled geiser-completion-module-list-func (#271)Jose Antonio Ortega Ruiz
2020-02-23Add Gambit source files to makefilesDavid Wilson
2020-02-14Refix #271, and consider gardening instead of programmingJose Antonio Ortega Ruiz
2020-02-13Guile: use load paths defined in dir-local variables (fixes #268)Jose Antonio Ortega Ruiz
A similar idea should probably be used with other schemes, but right now i feel ashamed of having taken so long to fix this one (assuming it's fixed!), so let's rush this commit for a change.
2020-02-13Proper wrapping of final comment lines (fixes #292)Jose Antonio Ortega Ruiz
Thanks a lot Sean Delvin for a great bug report which, moreover, contained the solution to the problem! (even though i'm risking a small modification).
2020-02-13Compatibility with Helm completions in emacs-25 (fixes #271)Jose Antonio Ortega Ruiz
2020-01-28Leftover (fixes #291)Jose Antonio Ortega Ruiz
Repeat with me: try M-x geiser-reload before pushing to gitlab
2020-01-28C-c \ and C-c [ in geiser-repl tooJose Antonio Ortega Ruiz
With a hat tip to Mikhail Kryshen, who was wondering in guile-user why oh why, and rightly so.
2019-11-26Rename multiline expression optionAaron Marks
* Renames geiser-repl-context-sensitive-send to geiser-repl-send-on-return-p. This option's value is now inverted. * Update documentation accordingly.
2019-10-25elisp/geiser-completion.el: Expose `--symbol-list` and `--module-list` funcs.Brian Leung
2019-10-21elisp/geiser.doc.el: Add geiser-doc-manual-for-symbol.Brian Leung
2019-10-12Missing require (fixes issue #285)Jose Antonio Ortega Ruiz
Seems we forgot a require while adding a new defcustom in geiser-log.
2019-09-03Add a few minor tweaks.Lockywolf
2019-09-03Fix latest chicken. Add debug level logging. Fixed typo.Lockywolf
2019-09-03Add a custom variable to scroll *geiser messages*.Lockywolf
2019-09-03Add a (declare (debug)) form to all geiser-%s--with-buffer macros.Lockywolf
2019-09-02Set header-line-format only in case when `cond` branch is trueAndrey Orst
2019-08-20add top level functionsmathieu2em
2019-08-20support gambit's style block comments from chris blommathieu2em
2019-08-20WIP gambit support first draftmathieu2em
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-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-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-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-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-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-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-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.
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-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-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