From: Efraim Flashner <efraim@flashner.co.il>
To: Foo Chuan Wei <chuanwei.foo@hotmail.com>
Cc: 30385@debbugs.gnu.org
Subject: [bug#30385] [bug#31989] vim-build-system
Date: Sun, 28 Nov 2021 11:28:10 +0200 [thread overview]
Message-ID: <YaNLqn+KdyRVoo2D@3900XT> (raw)
In-Reply-To: <PU1PR01MB215519BC63AF5C72157E60908D659@PU1PR01MB2155.apcprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Sun, Nov 28, 2021 at 09:23:30AM +0000, Foo Chuan Wei wrote:
> On 2021-11-26 13:13:38 +0200, Efraim Flashner wrote:
> > We do pretty well with the copy-build-system, with the occasional extra
> > phase(s).
>
> But the help tags files (`:help helptags`) are not generated when using
> the copy-build-system. Help tag files should be generated during the
> build phase for Vim plugins, because the user cannot generate help tags
> after plugin installation. The user does not have permission to modify
> anything in ~/.guix-profile/share/vim/vimfiles/, so `:helptags
> ~/.guix-profile/share/vim/vimfiles/` will fail.
I'm a bit rusty on the help tags. I thought they would all clober each
other if they were built during the package building, since they all
have the same name and we can only install one, but if we built them as
a profile hook then they'd all be able to co-exist.
Thoughts?
--
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 --]
next prev parent reply other threads:[~2021-11-28 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 20:04 [bug#31989] vim-build-system Efraim Flashner
2018-06-28 4:56 ` Nils Gillmann
2021-11-24 23:45 ` zimoun
2021-11-26 11:13 ` [bug#30385] " Efraim Flashner
2021-11-28 9:23 ` Foo Chuan Wei
2021-11-28 9:28 ` Efraim Flashner [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-07 22:30 [bug#30385] Add vim-build-system ng0
2018-02-28 8:54 ` ng0
2018-02-28 22:08 ` Ludovic Courtès
2018-06-21 13:20 ` Ricardo Wurmus
2018-06-26 14:47 ` Nils Gillmann
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=YaNLqn+KdyRVoo2D@3900XT \
--to=efraim@flashner.co.il \
--cc=30385@debbugs.gnu.org \
--cc=chuanwei.foo@hotmail.com \
/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).