unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix-edit  shows "Autodoc not available..." w/ 2 REPLs
Date: Tue, 12 Jul 2016 11:16:52 +0300	[thread overview]
Message-ID: <87oa63nudn.fsf@gmail.com> (raw)
In-Reply-To: <86furgyzxt.fsf@gmail.com> (myglc2@gmail.com's message of "Mon, 11 Jul 2016 11:09:02 -0400")

myglc2 (2016-07-11 18:09 +0300) wrote:

> Running guix/debian ...
>
> When I do 'M-x guix-edit RET screen RET' I get ...
>
> "Autodoc not available (No Geiser REPL for this buffer (try M-x run-geiser))"

Ouch, I've just answered you on #guix (using sneek).

This error is harmless.  It comes from Geiser and happens when you work
with any scheme file and did not start Geiser REPL.

Guix REPL is used only by "M-x guix-..." commands (to show/install
packages, open package files, etc.).  Guix REPL does not interfere with
a usual editing of scheme files.  I mean "M-x guix-edit ..." just opens
a scheme file with the package definition, and that's it.  If you need a
Geiser REPL (but it's unlikely you need it) while working with this
file, you can start it with C-c C-z.

BTW, if you don't want to use Geiser at all, you can disable it with
(setq geiser-mode-auto-p nil).  With this setting, scheme files will not
enable 'geiser-mode', so you will not see that autodoc error anymore.

> ... This puzzles me because guix already has 2 REPLs running ...
>
>  *  * Guile REPL *          1228 REPL             (Guile REPL<1> run)
>  *  *Guix REPL*              312 REPL             (Guile REPL run)
>
> So... I wonder, should I really need to start up another REPL?
>
> Or...  is something fishy with my setup?

No, it's OK.

> My .emacs.d/init.el file contains ...
>
> ***
> ;; start: guix emacs setup ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
> ;; to run emacs interface from git checkout and have guix-edit operate
> ;; on git checkout files
> (let ((dir "/home/g1/dev/guix/emacs"))
>   (add-to-list 'load-path dir)
>   (setq guix-load-path dir))
> (require 'guix-init nil t)

This should be (require 'guix-autoloads nil t) nowadays.  If you open
*Messages* buffer (C-h e), you can find the following message there:

  (require 'guix-init) is obsolete, use (require 'guix-autoloads) instead.

Try "M-x find-library guix-init" to see what it does.

-- 
Alex

  reply	other threads:[~2016-07-12  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 15:09 guix-edit shows "Autodoc not available..." w/ 2 REPLs myglc2
2016-07-12  8:16 ` Alex Kost [this message]
2016-07-12 14:22   ` myglc2
2016-07-12 20:56     ` Alex Kost
2016-07-14  0:12       ` myglc2
2016-07-15 17:31         ` Alex Kost
2016-07-16 15:07           ` myglc2
2016-07-19 17:54             ` Alex Kost
2016-07-19 21:18               ` myglc2
2016-07-18 13:05         ` myglc2
2016-07-19 16:39           ` Alex Kost

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=87oa63nudn.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=myglc2@gmail.com \
    /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).