unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: HiPhish <hiphish@posteo.de>
To: guix-devel@gnu.org
Subject: Re: Unofficial Neovim channel
Date: Tue, 22 Jan 2019 13:59:10 +0100	[thread overview]
Message-ID: <5377851.kt24CWoDkK@aleksandar-ixtreme-m5740> (raw)

> I wonder why you felt the need to have that channel?
Two points: the package in Guix is lagging behind in release, and I don't know 
enough yet about Guix to submit patches on a whim. So I made a channel to first 
try thing out for myself before submitting them to Guix. If I mess something 
up in my channel that's my problem, but if I mess up something in Guix then it 
reflects badly on all of Guix. I could have just left the channel local to my 
hard drive (as I had in the past), but making it public allows more people to 
have a look at it.

I guess most (all?) Guix package maintainers use Emacs instead of Vim or 
Neovim, but I use Neovim as my daily driver, so I'm more likely to catch if 
something is wrong. For example, I noticed that the Guix Neovim package is 
using Lua 5.2 libraries has its inputs, whereas you need Lua 5.1 libraries 
(Lua is not backwards-compatible). I had also submitted Lua 5.1 packages of 
lua-lpeg and lua-libmpack to Guix in the past.

> What's the difference between your definition and guix' definition?
Currently not much, only being three releases ahead and having the correct 
dependencies. (Lua 5.2 generally works as well, but you never know when an 
obscure edge-case might bite you in the rear)

             reply	other threads:[~2019-01-22 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 12:59 HiPhish [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-21 11:22 Unofficial Neovim channel HiPhish
2019-01-21 14:02 ` Ludovic Courtès
2019-01-22 11:14 ` Julien Lepiller
2019-01-22 15:08   ` Pjotr Prins

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=5377851.kt24CWoDkK@aleksandar-ixtreme-m5740 \
    --to=hiphish@posteo.de \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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