summaryrefslogtreecommitdiff
path: root/elisp
AgeCommit message (Collapse)Author
2013-07-01Experiment setting history file coding systemJose Antonio Ortega Ruiz
2013-07-01Preventing session.el messing up with geiser-doc--historyJose Antonio Ortega Ruiz
Session seems to be recovering the value of geiser-doc--history badly (see issue #7 for @achitu's discoveries), and since it is, in fact, not a good idea to save it anyway, we've added an eval-on-load deregistering the variable from session's list.
2013-06-27White space, reallyJose Antonio Ortega Ruiz
2013-06-20Another indentation rule: match-let-valuesJose Antonio Ortega Ruiz
2013-06-15Missing require cl for caseJose Antonio Ortega Ruiz
2013-06-10racket: new ,geiser-load command in REPLJose Antonio Ortega Ruiz
... and used also internally for C-c C-k, although it doesn't yet work as well as i wanted when it comes to load modules. The reason is probably in geiser/enter, where we don't record modification times per submodule but per path, which is not correct in the presence of submodules.
2013-06-09racket: module* and module+ denote submodules tooJose Antonio Ortega Ruiz
Recognizing those forms in the elisp module getter.
2013-06-09racket: indentation for module*Jose Antonio Ortega Ruiz
2013-06-06For crazy guys that use (define/match [foo bar] ...)Jose Antonio Ortega Ruiz
Racket is happy with that, so who are we to disagree?
2013-06-06Racket: correct font-lock for define/match, againJose Antonio Ortega Ruiz
We weren't considering the obvious: (define/match (foo bar) ...)
2013-06-06Racket: correct font lock for define/matchJose Antonio Ortega Ruiz
We could probably generalize to more function definition forms, but this is a start.
2013-05-21yank input if point is over history inputDarren Hoo
2013-05-13Add geiser-eval-buffer & geiser-eval-buffer-and-goNick Parker
These functions are similar to geiser-eval-region and geiser-eval-region-and-go, however they allow the user to operate on the entire buffer, not requiring the user to narrow to a specific region. This also differs slightly from geiser-compile-current-buffer as geiser-eval-buffer does not require the contents of the buffer to be saved prior to being sent to the REPL. Documentaion has also been updated to include references to the new methods and their keybindings.
2013-05-09guile: lambda* indentationAleix Conchillo Flaque
2013-04-21Fix for Racket compilation error jumping in REPLJose Antonio Ortega Ruiz
The backtraces now display some leading whitespace, which the default compilation-mode regexps was making part of the file name.
2013-04-21Racket: fixing error backtrace cleansingJose Antonio Ortega Ruiz
i.e., removing again references to geiser's innards
2013-04-17Racket: fix for jump to manual for symbols not in the namespaceJose Antonio Ortega Ruiz
We had broken using the hint that `help` offers during our recent adventures...
2013-04-15Racket: correct detection of manual lookup failuresJose Antonio Ortega Ruiz
Still a tad messy, because we are always forcing a retort-syntax error and checking its ouput, but good enough for now.
2013-04-15Racket: better help commandsJose Antonio Ortega Ruiz
For some reason that i don't fully understand, evaluating a function in the racket/base namespace first thing after loading errortrace breaks the help macro (!). This patches provides a workaround by actually invoking help first thing when Geiser starts, with alibi that it serves to preload the help index (in a separate thread). While i was at it, i improved the message printed in the minibuffer when no help is found.
2013-04-14Disabling company calls while the REPL is workingJose Antonio Ortega Ruiz
2013-04-13A better solution to the funky filename problemJose Antonio Ortega Ruiz
So, the problem was that our regexp for a Racket prompt didn't take into account that filenames could contain white spaces: "@[^ ]*> ". A simple solution was accepting them: "@[^>]+> " won't work because '>' is also a valid character in filenames, so we went for "@.*> ". The drawback is that finding the beginning of the prompt (e.g. in C-a) fails when you're writing things like: racket@foo bar.rkt> (> 2 3) because here comint believes that the prompt is "racket@foo bar.rkt> (> " And that could have side-effects elsewhere. So what i've done is simply changing the way white-space is (not) printed in the prompt, substituting it by underscores. That way, whe can go back to the initial regexp, comint doesn't get confused, and users can easily infer that "@foo_bar.rkt>" is actually referring to their "foo bar.rkt" file.
2013-04-13Another take at the fix (files with >, bleh)Jose Antonio Ortega Ruiz
2013-04-13Racket: accepting spaces within comint's promptJose Antonio Ortega Ruiz
Since spaces are allowed inside filenames after all.
2013-04-12A bit of documentation for the previous patchesJose Antonio Ortega Ruiz
2013-04-12Simplifications to previous patchJose Antonio Ortega Ruiz
2013-04-12Evaluate last expression to buffer with a prefixDiogo F. S. Ramos
Use a prefix before pressing C-x C-e to print the result of evaluating the expression before mark to the current buffer.
2013-04-12Hide auto-started REPLJose Antonio Ortega Ruiz
I'm not convinced that this is the right thing, and the effect is a bit ugly (we use save-window-excursion), but maybe this is the correct thing to do for users that want auto-start.
2013-04-11New flag to automatically start REPLs when geiser-mode is activatedJose Antonio Ortega Ruiz
When no live REPL is found, of course. The flag's imaginatively called geiser-mode-start-repl-p.
2013-04-10Fix for evaluations returning no resultJose Antonio Ortega Ruiz
Such as (values), which produce a retort of the form ((result) ...), which has nothing wrong in it! Thanks to Diogo.
2013-04-09New customizable geiser-repl-query-on-kill-pJose Antonio Ortega Ruiz
In case you don't care about killing live REPLs...
2013-04-02More Racket for/* forms indentation from DiogoJose Antonio Ortega Ruiz
2013-03-01Using implementation-specific keywords also in REPLJose Antonio Ortega Ruiz
And, while we're at it, honour the new case-sentive flag, as suggested by Diogo.
2013-03-01Indentation rule for match/values (Diogo F.S. Ramos)Jose Antonio Ortega Ruiz
2013-03-01Configurable keyword case sensitivityJose Antonio Ortega Ruiz
By default, keywords are now not fontified in Scheme buffers unless they have the correct (lower) case. This behaviour can be altered by new, per-implementation customization variables. Thanks to Diogo F. S. Ramos for pointing this out.
2013-02-20Indentation for match-letJose Antonio Ortega Ruiz
2013-02-09Indentation for Racket's structJose Antonio Ortega Ruiz
Thanks to Diogo F. S. Ramos.
2013-02-07Accepting ~ in geiser-add-to-load-pathJose Antonio Ortega Ruiz
2013-02-03Little cleanups, and C-u variant for the lambda thingJose Antonio Ortega Ruiz
2013-02-03More robust lambda and keybinding to C-c \Jose Antonio Ortega Ruiz
Since C-\ is a standard Emacs binding, and people know how to change it anyway. I've also put the command in the menu for Geiser mode, for discoverability. A pleasant surprise: greek lambdas are understood by both Racket and Guile.
2013-02-03Insert Greek letter lambda.Ray Racine
2013-01-22Using comint-dynamic-complete-filenameJose Antonio Ortega Ruiz
.. which seems to be available also in emacs 23.2 (although reports as to whether it works are mixed), and has better behaviour anyways.
2012-12-14Racket: indentation for `local'.Jose Antonio Ortega Ruiz
Hat tip Diogo F. S. Ramos.
2012-12-10Fix: more encompassing lookup for images in scheme outputJose Antonio Ortega Ruiz
We were not taking into account windows paths, with their backslashes and colons.
2012-11-11New command geiser-repl-clear-bufferJose Antonio Ortega Ruiz
Just renamed geiser-repl--clear-buffer (we don't use -- when users can call the command with M-x normally) and added documentation.
2012-11-09New function 'geiser-repl--clear-buffer'Jonas Rodrigues
2012-10-27Filename completion also in scheme buffersJose Antonio Ortega Ruiz
By means of a new entry in completion-at-point-functions that uses the handy comint-filename-completion.
2012-10-24Completing file names at the REPL, but only in string contextsJose Antonio Ortega Ruiz
2012-10-24Completing file names at the REPLJose Antonio Ortega Ruiz
When no other completion is available, that is.
2012-10-24Little clean-ups to the indentation rulesJose Antonio Ortega Ruiz
Splitting better the specially indented forms between our two implementations, so that users of a single one don't get weird indentations for froms without a special meaning in their scheme. Ideally, we should make these indentation rules buffer-local, so that when a user is in a, say, Guile buffer, module+ has no special indentation (as is the case now if that user also has activated support for Racket).
2012-10-24Racket: indentation for module+ formsJose Antonio Ortega Ruiz