From: Catonano <catonano@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Geiser documentation buffers
Date: Sun, 17 Jul 2016 13:15:49 +0200 [thread overview]
Message-ID: <CAJ98PDy5s6LGUqMxvEVSvSDKP0jMm+QdtrJfd_VFrk_y6sN68g@mail.gmail.com> (raw)
In-Reply-To: <87inw571dc.fsf@gnu.org>
[-- 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 --]
next prev parent reply other threads:[~2016-07-17 11:15 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 [this message]
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
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
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=CAJ98PDy5s6LGUqMxvEVSvSDKP0jMm+QdtrJfd_VFrk_y6sN68g@mail.gmail.com \
--to=catonano@gmail.com \
--cc=alezost@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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).