Geiser documentation buffers

Geiser documentation buffers

[Catonano]

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

This is not about Guix, admittedly. It's about Geiser

I tried to post on the Geiser mailing list 3 times, to no avail

So I'm trying here now. Supposedly Geiser is serving most of the people
hacking on Guix, so I hope this is not an outrageously off topic post

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
buffer that I started from in the first place

So I'd have to start all over again

I made a little screenshot, here
https://www.youtube.com/watch?v=mSr6Rs6R1a4

[-- Attachment #2: Type: text/html, Size: 933 bytes --]

Re: Geiser documentation buffers

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Catonano <catonano@gmail.com> writes:

> This is not about Guix, admittedly. It's about Geiser
>
> I tried to post on the Geiser mailing list 3 times, to no avail
>
> So I'm trying here now. Supposedly Geiser is serving most of the
> people hacking on Guix, so I hope this is not an outrageously off
> topic post
>
> 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 buffer that I started from in the first place
>
> So I'd have to start all over again
>
> I made a little screenshot, here
> https://www.youtube.com/watch?v=mSr6Rs6R1a4

This happens to me, too.  I don't know why.  I hope somebody can tell us
how to fix it!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: Geiser documentation buffers

[Ludovic Courtès]

Catonano <catonano@gmail.com> skribis:

> This is not about Guix, admittedly. It's about Geiser
>
> I tried to post on the Geiser mailing list 3 times, to no avail
>
> So I'm trying here now. Supposedly Geiser is serving most of the people
> hacking on Guix, so I hope this is not an outrageously off topic post
>
> 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
> buffer that I started from in the first place
>
> So I'd have to start all over again

It’s a bug that made its way in the last Geiser version, I think, but
ISTR that it’s fixed upstream.  Maybe Alex knows?

Ludo’.

Re: Geiser documentation buffers

[Catonano]

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

2016-07-16 22:51 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:

> Catonano <catonano@gmail.com> skribis:
>
> > This is not about Guix, admittedly. It's about Geiser
> >
> > I tried to post on the Geiser mailing list 3 times, to no avail
> >
> > So I'm trying here now. Supposedly Geiser is serving most of the people
> > hacking on Guix, so I hope this is not an outrageously off topic post
> >
> > 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
> > buffer that I started from in the first place
> >
> > So I'd have to start all over again
>
> It’s a bug that made its way in the last Geiser version, I think, but
> ISTR that it’s fixed upstream.  Maybe Alex knows?
>
> Ludo’.
>

Ludovic,

thank you. I have been replied to on the Geiser mailing list. My posts were
received, after all

I was suggested to try the melpa provided Geiser and that works.

Now, the version of the melpa provided Geiser is 20160617.954 and the
version of the Guix provided Geiser is 0.8.1 and I'm not sure how they can
be compared

The Geiser repository is unreachable now (
https://git.savannah.gnu.org/cgit/geiser.git )

There's a github copy here https://github.com/jaor/geiser
but I'm not sure about the branches I saw there

I'd wait for Alex to clarify things a bit

In the meantime, can I try geiser-next ? Or is it gonna break things
irreparably ?

[-- Attachment #2: Type: text/html, Size: 2519 bytes --]

Re: Geiser documentation buffers

[myglc2]

Catonano <catonano@gmail.com> writes:

> 2016-07-16 22:51 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
>
>     Catonano <catonano@gmail.com> skribis:
>     
[...]
>     > 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 ;-)

BTW, nice movie! - George

Re: Geiser documentation buffers

[myglc2]

myglc2 <myglc2@gmail.com> writes:

> Catonano <catonano@gmail.com> writes:
>
>> 2016-07-16 22:51 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
>>
>>     Catonano <catonano@gmail.com> skribis:
>>     
> [...]
>>     > 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 ;-)
>
> BTW, nice movie! - George

Forgot to mention, you also need ...

;; temporary hack for geiser 'C-c C-d C-d' bug
(load-file "~/.emacs.d/lisp/geiser/elisp/geiser.el")

;; To make sure to Guile finds source files from git checkout
(with-eval-after-load 'geiser-guile
  (add-to-list 'geiser-guile-load-path "~/src/guix"))

... in your emacs init file.  HTH

Re: Geiser documentation buffers

[Ludovic Courtès]

myglc2 <myglc2@gmail.com> skribis:

> Catonano <catonano@gmail.com> writes:
>
>> 2016-07-16 22:51 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
>>
>>     Catonano <catonano@gmail.com> skribis:
>>     
> [...]
>>     > 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 <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.
--8<---------------cut here---------------end--------------->8---

(Discussed at <https://github.com/jaor/geiser/issues/121>.)

Alex, Fede: how about backporting it in our package?

Ludo’.

Re: Geiser documentation buffers

[Alex Kost]

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

Re: Geiser documentation buffers

[Ludovic Courtès]

Alex Kost <alezost@gmail.com> skribis:

> 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>)

Perfect!

Ludo’.

Re: Geiser documentation buffers

[Catonano]

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

2016-07-18 17:48 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:

> > 'geiser-next' is already new enough to have this fix (myglc2 confirms:
> > <http://lists.gnu.org/archive/html/help-guix/2016-07/msg00133.html>)
>
> Perfect!
>
> Ludo’.
>
>
I want to thank all the people who participated in this thread.

I sincerely appreciated your help.

[-- Attachment #2: Type: text/html, Size: 874 bytes --]

Re: Geiser documentation buffers

[Alex Kost]

Catonano (2016-07-17 14:15 +0300) wrote:

> Ludovic,
>
> thank you. I have been replied to on the Geiser mailing list. My
> posts were received, after all
>
> I was suggested to try the melpa provided Geiser and that works.
>
> Now, the version of the melpa provided Geiser is 20160617.954 and the
> version of the Guix provided Geiser is 0.8.1 and I'm not sure how
> they can be compared

MELPA always contains the latest master, so it's much newer than 0.8.1.

> The Geiser repository is unreachable now ( https://
> git.savannah.gnu.org/cgit/geiser.git )

I wasn't aware about this repo, but the development happens on github.

> There's a github copy here https://github.com/jaor/geiser
> but I'm not sure about the branches I saw there

If you want to use a git checkout, use 'master' branch.

> I'd wait for Alex to clarify things a bit
>
> In the meantime, can I try geiser-next ? Or is it gonna break things
> irreparably ?

Absolutely not!  You can try it.  Actually the mentioned bug was one of
the main reason that Christopher added 'geiser-next' package.  I didn't
try it but it should work.  This is a simple checkout of a Geiser
commit, so it is as stable as MELPA.  'geiser-next' is more "fresh" than
0.8.1 but less fresh than MELPA (16 commits were made to Geiser since
'geiser-next' was added).

-- 
Alex

Re: Geiser documentation buffers

[myglc2]

Alex Kost <alezost@gmail.com> writes:

> Catonano (2016-07-17 14:15 +0300) wrote:
[...]
>> In the meantime, can I try geiser-next ? Or is it gonna break things
>> irreparably ?
>
> Absolutely not!  You can try it.  Actually the mentioned bug was one of
> the main reason that Christopher added 'geiser-next' package.  I didn't
> try it but it should work.

geiser-next exhibits the problem also.

Re: Geiser documentation buffers

[myglc2]

myglc2 <myglc2@gmail.com> writes:

> Alex Kost <alezost@gmail.com> writes:
>
>> Catonano (2016-07-17 14:15 +0300) wrote:
> [...]
>>> In the meantime, can I try geiser-next ? Or is it gonna break things
>>> irreparably ?
>>
>> Absolutely not!  You can try it.  Actually the mentioned bug was one of
>> the main reason that Christopher added 'geiser-next' package.  I didn't
>> try it but it should work.
>
> geiser-next exhibits the problem also.

Oops I take that back... geiser-next does fix the problem. 

Re: Geiser documentation buffers

[Alex Kost]

Ludovic Courtès (2016-07-16 23:51 +0300) wrote:

> Catonano <catonano@gmail.com> skribis:
>
>> This is not about Guix, admittedly. It's about Geiser
>>
>> I tried to post on the Geiser mailing list 3 times, to no avail
>>
>> So I'm trying here now. Supposedly Geiser is serving most of the people
>> hacking on Guix, so I hope this is not an outrageously off topic post
>>
>> 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
>> buffer that I started from in the first place
>>
>> So I'd have to start all over again
>
> It’s a bug that made its way in the last Geiser version, I think, but
> ISTR that it’s fixed upstream.  Maybe Alex knows?

Yes, it was actually me who suggested a fix :-)

The bug was originally reported by Federico:
<https://github.com/jaor/geiser/issues/121>.

To make it clear: the fix is in the Geiser master, but not in the latest
Geiser version (which is 0.8.1).

-- 
Alex