From: erwin <erwin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: alacritty-terminfo fails script, because ncurses is not installed
Date: Thu, 21 Jul 2022 04:50:08 +0200 [thread overview]
Message-ID: <20220721025008.FmWdBstv16vC6lAKO50R7zBS6bGzfpe6pP1fElhhzHU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34392@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
New comment by erwin on void-packages repository
https://github.com/void-linux/void-packages/issues/34392#issuecomment-1190977891
Comment:
When I run `toe -a` I'm getting:
```
toe -a >/dev/null
toe: couldn't open terminfo file alacritty.info.
```
Because of the file:
```
/usr/share/terminfo/a/alacritty.info
```
This is the only `.info` file under /usr/share/terminfo. All of the other files installed there have already been converted.
```
❯ find /usr/share/terminfo | grep info$
/usr/share/terminfo
/usr/share/terminfo/a/alacritty.info
```
Shouldn't this be packaged the way `kitty-terminfo` is?
```
❮ xbps-query -f kitty-terminfo
/usr/share/terminfo/x/xterm-kitty
```
Maybe terminfo/a/alacritty should be moved from `ncurses-term` to `alacritty-terminfo`?
```
xlocate /usr/share/terminfo/a/alacritty
alacritty-terminfo-0.10.1_1 /usr/share/terminfo/a/alacritty.info
ncurses-term-6.3_2 /usr/share/terminfo/a/alacritty
ncurses-term-6.3_2 /usr/share/terminfo/a/alacritty+common
ncurses-term-6.3_2 /usr/share/terminfo/a/alacritty-direct
```
next prev parent reply other threads:[~2022-07-21 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 12:52 [ISSUE] " hasufell
2021-12-11 3:19 ` [ISSUE] [CLOSED] " ericonr
2022-07-21 2:50 ` erwin [this message]
2022-07-21 7:17 ` meator
2022-07-21 7:44 ` erwin
2022-07-21 8:25 ` meator
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=20220721025008.FmWdBstv16vC6lAKO50R7zBS6bGzfpe6pP1fElhhzHU@z \
--to=erwin@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).