| Age | Commit message (Collapse) | Author |
|---|
|
... 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.
|
|
|
|
|
|
Recognizing those forms in the elisp module getter.
|
|
That is, complying to the submodule loading protocol (cf. racket's own
enter!).
|
|
|
|
And we display it (the current path, settable via ,cd) as a string.
This was, i'm sure, a secret command nobody is using!
|
|
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.
|
|
Racket is happy with that, so who are we to disagree?
|
|
We weren't considering the obvious: (define/match (foo bar) ...)
|
|
We could probably generalize to more function definition forms, but
this is a start.
|
|
|
|
|
|
|
|
|
|
|
|
A nit about the new commands docs, and thanks to Nick 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.
|
|
|
|
|
|
|
|
|
|
Almost all contributions have come this way, and it's a hassle having
two of them.
|
|
... since i've got reports that it's sometimes annoying not to be able
to directly click and post.
|
|
The backtraces now display some leading whitespace, which the default
compilation-mode regexps was making part of the file name.
|
|
i.e., removing again references to geiser's innards
|
|
We had broken using the hint that `help` offers during our recent
adventures...
|
|
Fixes #3 for real
|
|
And Dmitry is now maintaining it. Links updated, issue #3 fixed.
|
|
|
|
Still a tad messy, because we are always forcing a retort-syntax error
and checking its ouput, but good enough for now.
|
|
... by the obvious device of waiting for the thread building the index
to finish.
|
|
The evaluation of the help form must happen in a good enough
namespace.
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
Since spaces are allowed inside filenames after all.
|
|
|
|
|
|
Use a prefix before pressing C-x C-e to print the result of evaluating
the expression before mark to the current buffer.
|
|
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.
|
|
|
|
When no live REPL is found, of course. The flag's imaginatively
called geiser-mode-start-repl-p.
|
|
Such as (values), which produce a retort of the form ((result) ...),
which has nothing wrong in it! Thanks to Diogo.
|
|
In case you don't care about killing live REPLs...
|
|
|
