Github messages for voidlinux
 help / color / mirror / Atom feed
From: Zapeth <Zapeth@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Suggestion - Split `helix-grammars` from `helix` package
Date: Fri, 01 Sep 2023 15:14:32 +0200	[thread overview]
Message-ID: <20230901131432.avGr3AtHXtf-FCExt4W8wHmj_UOdPFQr0WFAlx_rmms@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45828@inbox.vuxu.org>

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

Closed issue by Zapeth on void-packages repository

https://github.com/void-linux/void-packages/issues/45828

Description:
The `helix` package by default includes all its compiled treesitter grammars, which take up the majority of the package size (~110MB or  86% of the total size in the latest release, see also https://github.com/helix-editor/helix/issues/6187).

While it is useful to have LSP support for all these languages out of the box, I think it should be up to the user to decide if its worth the extra space, especially since its likely to increase as more languages get added.

So my suggestion would be to split the grammar *.so at `/usr/lib/helix/runtime/grammars` in an extra package `helix-grammars` that depends on `helix`.

      parent reply	other threads:[~2023-09-01 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 18:38 [ISSUE] " Zapeth
2023-08-30 18:53 ` classabbyamp
2023-08-30 19:39 ` Zapeth
2023-08-30 20:00 ` Bnyro
2023-08-30 20:01 ` classabbyamp
2023-08-31 16:48 ` mhmdanas
2023-08-31 16:50 ` Bnyro
2023-08-31 17:06 ` tranzystorek-io
2023-08-31 17:10 ` mhmdanas
2023-08-31 17:23 ` classabbyamp
2023-08-31 19:04 ` mhmdanas
2023-09-01 13:14 ` Zapeth
2023-09-01 13:14 ` Zapeth [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=20230901131432.avGr3AtHXtf-FCExt4W8wHmj_UOdPFQr0WFAlx_rmms@z \
    --to=zapeth@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).