| Age | Commit message (Collapse) | Author |
|---|
|
At least by default.
|
|
|
|
`shell-command` assumes Bourne-shell-compatible quoting, which
doesn't work when the user isn't using a Bourne-compatible shell.
Instead of futzing about with quoting, we can just use `process-lines`
to execute a process and pass it arguments directly.
|
|
|
|
- Also cleaned up the namespace a little.
|
|
C-h P (`display-package') can make use of it.
|
|
|
|
... so that we don't interfere with other active backends, and following
the same policy as in the rest of company-mode geiser methods. See also
the discussion in github's #173.
|
|
As requested in github issue #173. Seems it's confusing people, which
is exactly the problem it was originally trying to avoid!
|
|
-This causes chicken to fail to run if it cannot find the required
modules for Geiser; and will tell the user that the module is missing.
|
|
This was causing confusion and bug reports on a semi-regular
basis. Disable it for now until a better solution is made.
|
|
|
|
Avoid redefining font-lock-ensure, so that haskell-mode doesn't get mad
at us. Should close github's #164.
|
|
|
|
|
|
|
|
|
|
|
|
When using a prompt regexp, comint's version of these commands
misbehave (they try to reuse forward-paragraph, and that's not quite
it), so we're implemeting our own here in a very straightforward way.
We also bind the usual C-c C-p and C-c C-n to them. It only remains to
b seen whether advising the original ones is worth the trouble.
|
|
|
|
This one should fix github's issue #132. There's still the glitch that
scheme strings are fontified without taking into account extra keywords.
|
|
Addresses github's #158, and its implementation is really easy (kudos to
fice-t, also for telling me about bound-and-true-p).
|
|
|
|
We were adding only the scheme-specific ones.
|
|
We were doing it before the buffer's implementation, and the
implementation-specific keywords were not found. Should fix github's
issue #159.
|
|
Let's see if i finally got this right...
|
|
I wonder if this has ever worked fine: geiser-debug--display-retort was
a little mess. It should be a bit better now, but Guile is still
displaying funny messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes a regression introduced by commit
424553e017718c54e219212b27a32b341ec6bd28.
|
|
This is a fix similar to the one made in commit
8e75455dfbd46355d777c26366e7ccfcb59ace20.
|
|
|
|
Avoid calling 'geiser-con--request-string' twice by wrapping it into
'let'.
|
|
This fixes 2 issues:
1. Reconnecting to a remote process prompts for host/port, although it
is not needed.
2. 'geiser-connect' should be used only if 'geiser-repl--address' is a
host/port pair. When it is a socket file name,
'geiser-connect-local' should be used.
|
|
Because Chicken allows symbols to be imported with prefixes, and because
'apropos' does not provide any utility to match with the loaded
prefixes, it is difficult to acquire information about prefixed symbols.
This solution hacks around the issue by providing naive
fuzzy-matching. If no match for a symbol can be found then the first
character is dropped and matching is attempted again; the process is
repeated until matches are found or the entire symbol is consumed.
Also removes the (now redundant and slow) geiser-chicken-prefix-delimiters.
|
|
company-backends should not be overridden by modes, as users may have
additional backends that they wish to use. The appropriate behaviour is
to add your backend to the company-backends list.
Also removed the overriding of what ought to be user-controlled variables.
|
|
|
|
As patiently pointed out by Alex Kost in the discussion of issue #121,
using the macro defined by the geiser-popup--define macro before its
actual definition causes problems when geiser is loaded after
compilation. Thanks again, Alex and Federico.
|
|
We could probably be even more robust, but i am being a bit lazy
instead.
|
