Github messages for voidlinux
 help / color / mirror / Atom feed
From: maybe-one-day-ubermensch <maybe-one-day-ubermensch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] meson: copy vim files to neovim's runtime dir
Date: Thu, 24 Sep 2020 22:47:49 +0200	[thread overview]
Message-ID: <20200924204749.Ke1MJ0rdKL5zi-Q8xc0_ZJzvNp71xIIQGrSpj_59kLU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25054@inbox.vuxu.org>

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

There is an updated pull request by maybe-one-day-ubermensch against master on the void-packages repository

https://github.com/maybe-one-day-ubermensch/void-packages meson-nvim-files
https://github.com/void-linux/void-packages/pull/25054

meson: copy vim files to neovim's runtime dir


A patch file from https://github.com/void-linux/void-packages/pull/25054.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-meson-nvim-files-25054.patch --]
[-- Type: text/x-diff, Size: 1237 bytes --]

From 283a728811ccf5ff4adfc614479a1be38dc414c2 Mon Sep 17 00:00:00 2001
From: Jony <maybe-one-day-ubermensch@protonmail.com>
Date: Wed, 23 Sep 2020 09:37:01 -0700
Subject: [PATCH] meson: copy vim files to neovim's runtime dir

---
 srcpkgs/meson/template | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/meson/template b/srcpkgs/meson/template
index 2c1bbbc74f6..7a4277747eb 100644
--- a/srcpkgs/meson/template
+++ b/srcpkgs/meson/template
@@ -1,8 +1,7 @@
 # Template file for 'meson'
 pkgname=meson
 version=0.55.3
-revision=1
-archs=noarch
+revision=2
 build_style=python3-module
 hostmakedepends="python3-devel python3-setuptools"
 depends="ninja python3-setuptools"
@@ -28,6 +27,13 @@ post_install() {
 	vmkdir usr/share/vim/vimfiles
 	cp -rt ${DESTDIR}/usr/share/vim/vimfiles data/syntax-highlighting/vim/*/
 
+	for dir in ftdetect ftplugin indent plugin syntax; do
+		nvim_runtime_dir="usr/share/nvim/runtime/$dir"
+		vmkdir $nvim_runtime_dir
+
+		ln -sf /usr/share/vim/vimfiles/$dir/meson.vim ${DESTDIR}/$nvim_runtime_dir
+	done
+
 	vinstall data/syntax-highlighting/emacs/meson.el 644 usr/share/emacs/site-lisp
 	vinstall data/shell-completions/zsh/_meson 644 usr/share/zsh/site-functions
 }

  parent reply	other threads:[~2020-09-24 20:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 16:41 [PR PATCH] " maybe-one-day-ubermensch
2020-09-23 16:45 ` sgn
2020-09-23 16:47 ` sgn
2020-09-23 17:14 ` maybe-one-day-ubermensch
2020-09-23 17:14 ` [PR PATCH] [Closed]: " maybe-one-day-ubermensch
2020-09-24 15:47 ` maybe-one-day-ubermensch
2020-09-24 16:09 ` Johnnynator
2020-09-24 20:47 ` maybe-one-day-ubermensch [this message]
2020-09-24 20:48 ` maybe-one-day-ubermensch
2020-09-25 23:14 ` [PR PATCH] [Updated] " maybe-one-day-ubermensch
2020-10-09 23:16 ` [PR PATCH] [Closed]: " ericonr
2020-10-09 23:17 ` ericonr
2020-10-10  2:09 ` maybe-one-day-ubermensch

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=20200924204749.Ke1MJ0rdKL5zi-Q8xc0_ZJzvNp71xIIQGrSpj_59kLU@z \
    --to=maybe-one-day-ubermensch@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).