You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-bash
set -o vidirective does not work at all.set -o vi(orset -o emacs) works if you enable it at compile time (configure --with-libedit), but the point of dash is to provide a simple robust and efficient interpreter for the sh language that can be used forsystem()/popen()or interpret#! /bin/sh -scripts. It's not intended for interactive use. Look at shells likezshorfishfor that.dashto be POSIX complaint all the time if it is not?set -o viis very clearly part of the standard for/bin/sh. FWIW, I have no interest in using something likezshorfish. I guess I will just stick withksh88-based implementations. I doubt a simple recompile will fix all of the discrepancies anyway. Thanks for the reply.dashsupportsset -o vi(note that in bash, the vi mode is also optional and can be disabled at build time). POSIX specifies a standard API. IMO, the shell's line editor does not belong there and should be removed from the standard or at least moved to the User Portability option. For instance, that line editor does not make sense on embedded systems. Note that ksh88 has many non-compliances and bugs, far more so thandash. If you want a more compliant shell, you can have a look at bosh or yash (each also coming with their own issues).