From: Chris Marusich <cmmarusich@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Geiser documentation buffers
Date: Sat, 16 Jul 2016 13:06:02 -0700 [thread overview]
Message-ID: <87bn1xmjpx.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDzmb7Q9QZMuL5N4h8YimoTki6wHcUQv+DJM62myh1rDnw@mail.gmail.com> (catonano@gmail.com's message of "Sat, 16 Jul 2016 20:55:10 +0200")
[-- 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 --]
next prev parent reply other threads:[~2016-07-16 20:06 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 [this message]
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
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=87bn1xmjpx.fsf@gmail.com \
--to=cmmarusich@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.