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