From: erwin <erwin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bug: The configure option of dash is not POSIX compatible.
Date: Fri, 12 Aug 2022 12:41:10 +0200 [thread overview]
Message-ID: <20220812104110.GU5nxlfZE5tCVvhoMBy9aXc27vvyf5iFccB8XznZ51g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35457@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
New comment by erwin on void-packages repository
https://github.com/void-linux/void-packages/issues/35457#issuecomment-1212973026
Comment:
I realize this issue is closed, but I would ask you to reconsider including `--with-libedit` with `dash` on usability grounds.
1, This week I did a full re-install of void, and while making some changes to `/etc/fstab` ended up getting dropped into single user mode a few times... Sure you can start another shell, but it's fairly painful to use dash without even basic command line editing.
2, Also, Docker is hardcoded to use `/bin/sh` for build files... So when using dash to troubleshoot individual `RUN` commands from a Dockerfile, would be nice to have some basic command line editing.
3, Those are two examples that I ran into this week. Without line editing, it's just so unfriendly... Like a trip back to a pre-Linux terminal.
4. It's only 219K (though dash is only 123K), and I don't think dash is statically linked anyway.
Bottom line, dash exists there because sometimes we do actually have to use it, and when we do have to, it's usually in a troublesome time (like single user mode).
Thanks for taking the time to read this.
prev parent reply other threads:[~2022-08-12 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 10:58 [ISSUE] " carbongreat13
2022-02-08 16:12 ` leahneukirchen
2022-02-08 16:12 ` [ISSUE] [CLOSED] " leahneukirchen
2022-08-12 10:41 ` erwin [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=20220812104110.GU5nxlfZE5tCVvhoMBy9aXc27vvyf5iFccB8XznZ51g@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).