From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: myglc2 <myglc2@gmail.com>,
help-guix@gnu.org, Federico Beffa <beffa@ieee.org>
Subject: Re: Geiser documentation buffers
Date: Mon, 18 Jul 2016 11:14:18 +0300 [thread overview]
Message-ID: <87eg6rpdlx.fsf@gmail.com> (raw)
In-Reply-To: <87shv812et.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 17 Jul 2016 21:37:46 +0200")
Ludovic Courtès (2016-07-17 22:37 +0300) wrote:
> myglc2 <myglc2@gmail.com> skribis:
[...]
>> geiser-next also has the problem.
It doesn't :-)
>> I also hit "when pressing q the buffer won't close". An install from
>> https://github.com/jaor/geiser.git to ~./emacs.d/lisp works for me ;-)
>
> On closer inspection, it seems to be fixed by this commit:
>
> commit 8e75455dfbd46355d777c26366e7ccfcb59ace20
> Author: Jose Antonio Ortega Ruiz <jao@gnu.org>
> Date: Sun Dec 27 04:11:50 2015 +0100
>
> Avoiding uses of geiser-doc--with-buffer before its definition
>
> 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.
>
> (Discussed at <https://github.com/jaor/geiser/issues/121>.)
>
> Alex, Fede: how about backporting it in our package?
'geiser-next' is already new enough to have this fix (myglc2 confirms:
<http://lists.gnu.org/archive/html/help-guix/2016-07/msg00133.html>)
--
Alex
next prev parent reply other threads:[~2016-07-18 8:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 18:55 Geiser documentation buffers Catonano
2016-07-16 20:06 ` Chris Marusich
2016-07-16 20:51 ` Ludovic Courtès
2016-07-17 11:15 ` Catonano
2016-07-17 19:10 ` myglc2
2016-07-17 19:17 ` myglc2
2016-07-17 19:37 ` Ludovic Courtès
2016-07-18 8:14 ` Alex Kost [this message]
2016-07-18 15:48 ` Ludovic Courtès
2016-07-18 20:05 ` Catonano
2016-07-17 20:05 ` Alex Kost
2016-07-17 21:33 ` myglc2
2016-07-17 21:41 ` myglc2
2016-07-17 20:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg6rpdlx.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--cc=help-guix@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.