From: myglc2 <myglc2@gmail.com>
To: help-guix@gnu.org
Subject: Re: Geiser documentation buffers
Date: Sun, 17 Jul 2016 17:33:27 -0400 [thread overview]
Message-ID: <cu760s4lzko.fsf@gmail.com> (raw)
In-Reply-To: 87d1mcrpw9.fsf@gmail.com
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.
next prev parent reply other threads:[~2016-07-17 21:36 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
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 [this message]
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=cu760s4lzko.fsf@gmail.com \
--to=myglc2@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.
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).