all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Catonano <catonano@gmail.com>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Geiser documentation buffers
Date: Sat, 16 Jul 2016 22:51:27 +0200	[thread overview]
Message-ID: <87inw571dc.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDzmb7Q9QZMuL5N4h8YimoTki6wHcUQv+DJM62myh1rDnw@mail.gmail.com> (catonano@gmail.com's message of "Sat, 16 Jul 2016 20:55:10 +0200")

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’.

  parent reply	other threads:[~2016-07-16 20:51 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 [this message]
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
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=87inw571dc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=catonano@gmail.com \
    --cc=help-guix@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.
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.