From mboxrd@z Thu Jan 1 00:00:00 1970 From: HiPhish Subject: Re: Bringing the Neovim package up to date Date: Tue, 11 Sep 2018 13:12:13 +0200 Message-ID: <3517986.spaqn1PHyG@aleksandar-ixtreme-m5740> References: <33416237.peXBRamUYO@aleksandar-ixtreme-m5740> <87d0tlh71l.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38560) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fzgax-0006HY-6j for guix-devel@gnu.org; Tue, 11 Sep 2018 07:12:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fzgas-0004mN-2u for guix-devel@gnu.org; Tue, 11 Sep 2018 07:12:35 -0400 Received: from mout02.posteo.de ([185.67.36.66]:42485) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fzgar-0004ka-N9 for guix-devel@gnu.org; Tue, 11 Sep 2018 07:12:29 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id A1F8021607 for ; Tue, 11 Sep 2018 13:12:25 +0200 (CEST) In-Reply-To: <87d0tlh71l.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?ISO-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org On Monday, 2018-09-10 14:27:02 CEST Ludovic Court=C3=A8s wrote: > Sure! While you=E2=80=99re trying things out, you may find that IRC will= be > better suited to get guidance and information on how to debug issues. OK, noted. > Yes. In short you would define the new package to =E2=80=9Cinherit=E2=80= =9D from > =E2=80=98lua-5.1=E2=80=99, and you would change its =E2=80=98inputs=E2=80= =99 field. There are examples > of that in the code. Let us know if anything=E2=80=99s unclear! I'll give it a try, I just wanted to know if there is maybe something more = to=20 it to be aware of. > We cannot #:select from (gnu packages =E2=80=A6) modules due to the way G= uile > handles circular dependencies among modules. However we could use > select more frequently for other modules. I didn't know about circular dependencies. I mainly wanted to know if there= is=20 maybe a reason or guideline against using `#:select` and whether package=20 definitions like that might get rejected. > I don=E2=80=99t know if there=E2=80=99s anything similar for (Neo)Vim, bu= t those of us > who use Emacs also use Geiser, which displays in the =E2=80=9Cmode line= =E2=80=9D at the > bottom the module that provides a given variable. That explains a lot. I know about Geiser, but Vim is the editor I have sett= led=20 in, I feel that switching would be just as much work as porting Geiser to=20 Neovim at this point. From what I understand Geiser has two parts: the Emac= s=20 plugin and the actual Geiser process which is written in Scheme. "Porting"= =20 Geiser would only require re-writing the editor interface for Neovim while = the=20 Scheme backend could be kept. It's just that no one has ever felt the need = to=20 do that, Lisp programmers who use Vim are very rare. Is there a way to get the module from a REPL? I can run a REPL in my editor= ,=20 that's the crutch I have been using so far. (IMO tying the readability of t= he=20 source code to the development environment is a bad idea, that's what IDEs= =20 always end up doing)