From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ncurses-base as dependency to nano and bash/ncurses-libs
Date: Sat, 30 Jan 2021 15:44:54 +0100 [thread overview]
Message-ID: <20210130144454.8p0ZiWfBMCo7zDUWVteMfgCwIZIEWsTbl5jxyThsDfY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14488@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
Closed issue by am11 on void-packages repository
https://github.com/void-linux/void-packages/issues/14488
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 4.9.184-linuxkit x86_64-musl GenuineIntel uptodate rF`
* package:
`bash-5.0.009_1`
`nano-4.4_1`
### Expected behavior
With `base-minimal` (voidlinux-musl docker e.g.), when we install bash or nano, these packages should install ncurses-base package for the software to function.
### Actual behavior
After some googling and figuring out, it appears that the `ncurses-base` (and more granually, what Alpine Linux ports calls `ncurses-terminfo-base`) package is the one which is missing.
### Steps to reproduce the behavior
nano:
```sh
docker run -it voidlinux/voidlinux-musl dash
# inside the container
xbps-install -S
xbps-install -y nano
nano
# terminates with:
Error opening terminal: xterm.
# to fix the error
xbps-install ncurses-base
nano # it works!
```
bash:
```sh
docker run -it voidlinux/voidlinux-musl dash
# entered the container
xbps-install -S
xbps-install -y bash
bash
# entered bash
# type something and press ENTER
ls
# type something again and press ENTER
cd
# now press UP and UP, it looks like:
cdls
#instead of
ls
# similarly, back arrow key to navigate cursor does not move the caret.
# also, BACKSPACE renders spaces instead of erasing the character at caret.
# etc.
# to fix these issues
xbps-install ncurses-base
# exit and reenter bash to get the keybindings behave correctly
```
next prev parent reply other threads:[~2021-01-30 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 5:49 [ISSUE] " voidlinux-github
2019-10-05 13:49 ` voidlinux-github
2019-10-05 13:56 ` voidlinux-github
2021-01-30 3:03 ` ericonr
2021-01-30 4:49 ` sgn
2021-01-30 14:44 ` ericonr
2021-01-30 14:44 ` ericonr [this message]
2021-01-30 15:55 ` am11
2021-01-30 16:00 ` Duncaen
2021-01-30 16:03 ` Duncaen
2021-01-30 16:03 ` Duncaen
2021-01-30 16:39 ` am11
2021-01-30 16:45 ` Duncaen
2021-01-30 16:46 ` Duncaen
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=20210130144454.8p0ZiWfBMCo7zDUWVteMfgCwIZIEWsTbl5jxyThsDfY@z \
--to=ericonr@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).