all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org
Subject: Re: Neovim plugin/addon packaging
Date: Mon, 3 May 2021 08:46:06 +0300	[thread overview]
Message-ID: <YI+OHsty/RO7NpGo@3900XT> (raw)
In-Reply-To: <alpine.DEB.2.21.2105030042070.2109@marsh.hcoop.net>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Mon, May 03, 2021 at 12:46:30AM -0400, Jack Hill wrote:
> On Sun, 2 May 2021, Efraim Flashner wrote:
> 
> > ng0/nikita thought about it a few years ago but I think the
> > copy-build-system works well enough. I know for vim we need a vim
> > profile hook to create the documentation, does neovim need something
> > like that too?
> 
> I'm not sure and will need to investigate. With the XDG_DATA_DIRS search
> path, if I install neovim and neovim-syntastic into the same environment, I
> am able to see references to the syntastic documentation in the main help
> index, but trying to navigate to them results in a 'E149: Sorry, no help for
> syntastic-checkers.txt' error, so clearly something is not quite right.
> 

That's always something we can fix later. It's also not more broken than
it is now.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-05-03  5:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  5:03 Neovim plugin/addon packaging Jack Hill
2021-04-30 12:19 ` Efraim Flashner
2021-05-01 20:25   ` Jack Hill
2021-05-02  9:19     ` Efraim Flashner
2021-05-03  4:46       ` Jack Hill
2021-05-03  5:46         ` Efraim Flashner [this message]

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=YI+OHsty/RO7NpGo@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    /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.