summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-07-01NEWS updateJose 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-27Racket: not loading errortrace by defaultJose Antonio Ortega Ruiz
The new submodules and errortrace interact badly, for what i've seen. In particular, even with the submodule[+*] loading correctly, its namespace doesn't have all identifiers bound, and new ones seem to appear in the bindings lists (things like a.1 or b.2, when a and b are the actual identifiers defined inside the module). Since moreover someone mentioned in the devel ML that errortrace is in general terms buggy, i guess we can leave without it for the time being.
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-11racket: ,cd accepting also non-quoted pathsJose Antonio Ortega Ruiz
just because we can
2013-06-11racket: struggling with submodulesJose Antonio Ortega Ruiz
Submodule (re)loading is not without pecularities. In particular, module[*+] submodules are not visited the first time one enters its parent, but once you load them once, they're revisited every time we load the parent afterwards--racket's native enter! exhibits the same behaviour, so i'm guessing we'll have to live with that. There is however a glitch in that submodules can only be reloaded then by loading the parent, so we need to confirm that this is expected behaviour and, if it is, automating the parent's load when the submodule's is requested. On the other hand, entering a module[*+] is not working in Geiser yet, and it does in plain racket, so this one is our fault. Working on it.
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-10NitsJose Antonio Ortega Ruiz
2013-06-09racket: C-u C-c C-z on a submodule enters itJose Antonio Ortega Ruiz
2013-06-09racket: module* and module+ denote submodules tooJose Antonio Ortega Ruiz
Recognizing those forms in the elisp module getter.
2013-06-09racket: handling correctly submodules in load handler during ,enterJose Antonio Ortega Ruiz
That is, complying to the submodule loading protocol (cf. racket's own enter!).
2013-06-09racket: indentation for module*Jose Antonio Ortega Ruiz
2013-06-08racket: ,gcd -> ,pwdJose Antonio Ortega Ruiz
And we display it (the current path, settable via ,cd) as a string. This was, i'm sure, a secret command nobody is using!
2013-06-08racket: ,enter submodulesJose Antonio Ortega Ruiz
It is now possible to ,enter racket submodules. This is only the first part of the story, because evalations should take place in the submodule, not in its top level module, as it happens now.
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-06-04Ludovic made it also to AUTHORS and NEWSJose Antonio Ortega Ruiz
2013-06-04Guile: Fix subr argument name retrieval for Guile >= 2.0.9.Ludovic Courtès
2013-05-21Authors and news updated to include DarrenJose Antonio Ortega Ruiz
2013-05-21yank input if point is over history inputDarren Hoo
2013-05-14Nits in geiser-racket.shJose Antonio Ortega Ruiz
2013-05-14Documentation updatesJose Antonio Ortega Ruiz
A nit about the new commands docs, and thanks to Nick Parker.
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-05-04Release date for the webJose Antonio Ortega Ruiz
2013-05-03NEWS for 0.40.4Jose Antonio Ortega Ruiz
2013-04-28Thanks where thanks are dueJose Antonio Ortega Ruiz
2013-04-28Issue tracker links pointing to Github'sJose Antonio Ortega Ruiz
Almost all contributions have come this way, and it's a hassle having two of them.
2013-04-28Mailto link for the witty geiser-users addressJose Antonio Ortega Ruiz
... since i've got reports that it's sometimes annoying not to be able to directly click and post.
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-15Remainin reference to company's screencast gone.Jose Antonio Ortega Ruiz
Fixes #3 for real
2013-04-15Company mode screencast seems gone for goodJose Antonio Ortega Ruiz
And Dmitry is now maintaining it. Links updated, issue #3 fixed.
2013-04-15NEWS entry since Diogo confirmed things work againJose Antonio Ortega Ruiz
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: ensuring the first C-c C-d C-i worksJose Antonio Ortega Ruiz
... by the obvious device of waiting for the thread building the index to finish.
2013-04-15Racket: fixing help when REPL is in a moduleJose Antonio Ortega Ruiz
The evaluation of the help form must happen in a good enough namespace.
2013-04-15Racket: pre-loading help also in remote REPLsJose Antonio Ortega Ruiz
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-14More good NEWSJose Antonio Ortega Ruiz
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-13Good NEWSJose 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