| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is controlled by the new customizable variable
geiser-debug-treat-ansi-colors, which can be set to either nil (do
nothing), 'colors (fontify colors) or 'remove (just strip all ANSI
codes).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* elisp/geiser-repl.el(geiser-repl--sentinel): Use `substitute-command-keys'.
|
|
Also add a FIXME comment about how this macro isn't actually needed.
|
|
The whole first sentence should fit on the first line. If that makes
the line a bit long then that is unfortunate but better than wrapping
it onto a new line. When wrapping onto a new line anyway then the
second line should never be intended. When it can be avoided, then
long first lines should be made shorter.
|
|
This makes it possible to re-evaluate the containing
buffers without user customizations being clobbered.
|
|
|
|
|
|
|
|
The plan is to have geiser-core contain only, well, the elisp core
engine. The autotools scafolding is no really worth it, so it's gone
too (and in the process, i'll look younger).
|
|
When evaluating expressions in a Scheme buffer, display the error
of an evaluation in the minibuffer regardless of whether
`geiser-debug-show-debug-p` or `geiser-debug-jump-to-debug-p` are
set or not.
|
|
|
|
|
|
|
|
|
|
|
|
Should close issue #315, where it is pointed out that "sequences
consisting of `C-c` and a letter (either upper or lower case) are
reserved for users; they are the *only* sequences reserved for users,
so do not block them."
|
|
For no good reason, we were transforming numbers in retorts to symbols
and then failing to recognise things like line or column numbers
there.
The "fix" here only works for the intersection of numbers that are
written in the same way in elisp and scheme; one day we'll find a
situation where this doesn't cut it, but right now we only really use
integers.
|
|
Restoring what seem reasonable definitions for the completion
functions when called away from the current buffer. Should fix issue
|
|
|
|
|
|
Starting with Emacs 27 cl is fully deprecated, including at
compile-time.
|
|
|
|
|
|
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.
|
|
It's the convention and by following it we make a big step towards
supporting outline navigation.
|
|
|
|
|
|
|
|
|
|
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.
|
|
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).
|
|
|
|
Repeat with me: try M-x geiser-reload before pushing to gitlab
|
|
With a hat tip to Mikhail Kryshen, who was wondering in guile-user why
oh why, and rightly so.
|
|
* Renames geiser-repl-context-sensitive-send to
geiser-repl-send-on-return-p. This option's value is now inverted.
* Update documentation accordingly.
|
