From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Geiser documentation buffers Date: Sun, 17 Jul 2016 21:37:46 +0200 Message-ID: <87shv812et.fsf@gnu.org> References: <87inw571dc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOrt0-0003Z1-CN for help-guix@gnu.org; Sun, 17 Jul 2016 15:37:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bOrsy-0000U3-Ci for help-guix@gnu.org; Sun, 17 Jul 2016 15:37:57 -0400 In-Reply-To: (myglc2@gmail.com's message of "Sun, 17 Jul 2016 15:10:47 -0400") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: myglc2 Cc: Alex Kost , help-guix@gnu.org, Federico Beffa myglc2 skribis: > Catonano writes: > >> 2016-07-16 22:51 GMT+02:00 Ludovic Court=C3=A8s : >> >> Catonano skribis: >>=20=20=20=20=20 > [...] >> > When I ask Geiser to open the documentation buffer on some >> symbol at point, >> > then when pressing q the buffer won't close. A q will appear in >> the buffer >> > and it will persist. >> > >> > C-x k closes not only the documentation buffer but also the >> source code > [...] >> In the meantime, can I try geiser-next ? Or is it gonna break things >> irreparably ? > > geiser-next also has the problem. > > 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: --8<---------------cut here---------------start------------->8--- commit 8e75455dfbd46355d777c26366e7ccfcb59ace20 Author: Jose Antonio Ortega Ruiz Date: Sun Dec 27 04:11:50 2015 +0100 Avoiding uses of geiser-doc--with-buffer before its definition =20=20=20=20 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. --8<---------------cut here---------------end--------------->8--- (Discussed at .) Alex, Fede: how about backporting it in our package? Ludo=E2=80=99.