| Age | Commit message (Collapse) | Author |
|---|
|
|
|
So the generated tarball from `make dist' will have `dir' inside.
|
|
If a user doesn't want to install geiser, it's possible to run it in
place by loading `elisp/geiser.el' directly.
It's also possible to read the info manual directly but it's
inconvenient to not have it listed when hitting C-h i inside Emacs.
To list such manual, it's necessary to tell info where to look for it.
One way of doing it is adding the directory to the variable
`Info-additional-directory-list'. But, for this to work, there's need
to be a `dir' file listing the info manual.
|
|
The parser in geiser-syntax is (tail, but elisp doesn't care)
recursive, and we are setting max-lisp-eval-depth to some, ahem,
heuristic value before starting a read. For long strings, such as
that returned by the list of identifiers exported by the racket
module, the heuristic was bad enough to produce a value making Emacs
to blow away.
This is just a palliative. The real solution is turn the recursion in
geiser-syntax--read into an explicit iteration.
|
|
We were using a history entry separator including \0 that wasn't
writeable as an utf-8 file. Changing the separator to \n}{\n allows
using UTF-8 characters in the REPL which are correctly read back.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
|
|
|
|
just because we can
|
|
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.
|
|
... 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.
|
