unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luther Thompson <lutheroto@gmail.com>
To: help-guix@gnu.org
Subject: How do I cope with Geiser in Emacs
Date: Sat, 1 Dec 2018 19:34:46 -0500	[thread overview]
Message-ID: <20181201193446.38ce529b@gmail.com> (raw)

I don't know where to ask about this, but since the problem seems to
involve many interconnected Emacs-related packages, I'll see if you
guys can help.

When I'm editing a Scheme file (not Guix-related) in Emacs and
company-mode activates, I get this error message: 'Company: backend
company-capf error "No Geiser REPL for this buffer (try M-x
run-geiser)" with args (prefix)'. If I appease the error by running M-x
run-geiser, I get completion lists that don't make much sense. They
fail to include names that are already in the file, and they do include
what appear to be many obscure library functions.

I would expect company mode to fall back to a backend that doesn't
throw an error, but the strange completion lists that I get with Geiser
suggest that the problem is more complicated than that.

Here's what I've been able to figure out so far:

emacs-geiser is a propagated input of emacs-guix. (I don't directly use
emacs-geiser.)

company-capf is a backend for company-mode.

While in Scheme mode, company-capf must be indirectly calling some
function that throws this error.


Is there some kind of configuration I can do to fix this? There are so
many different Elisp files that might be involved, I don't know where
to start looking for a solution.

Thanks,
Luther

             reply	other threads:[~2018-12-02  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02  0:34 Luther Thompson [this message]
2018-12-02 20:43 ` How do I cope with Geiser in Emacs Alex Kost
2018-12-03  8:35   ` Luther Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181201193446.38ce529b@gmail.com \
    --to=lutheroto@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).