Tag Info

New answers tagged

0

Shells have two uses: to run scripts, and for an interactive command line. Dash is designed to be a fast, efficient shell for scripting. It has next to no nice features for interactive use. It doesn't have fancy prompts, command line edition, command history. It doesn't run a configuration file like bash's .bashrc when you start it interactively┬╣. You can ...


1

You can easily try things out for yourself and see if they are working without changing your current login shell. Apart from /etc/profile and ~/.profile, dash will read the file pointed to by an environment variable ENV when starting interactively so: ENV=~/.bashrc dash or better make a copy of your ~/.bashrc to ~/.dashrc and comment out/delete what you ...


3

Lots of the commands in your .bashrc are bash-specific. Things like HISTCONTROL aren't relevant to dash. Likewise for the command completion. Aliases will work however. Read the manpage for dash and check the manpage for each thing you're doing in your .bashrc to see whether it's applicable to dash. The real question you're asking is not very clear: do you ...


1

No, dash doesn't have completion. Otherwise it would be called bash. Dash was designed to execute shell scripts fast and with a minimum of memory, it wasn't intended to be used interactively. The best way to get completion in dash is to run exec zsh or exec fish. If you want to stick with dash, you can do what people did before completion existed: use ...


3

Dash is designed to be a minimal shell for fast script execution. Being comfortable for interactive use is very much not a design goal. If you want a fancy prompt, use a shell designed for interactive use: zsh, fish, or at least bash. The escape sequences you show are for bash. Dash does expand variables in the prompt, so you can set a prompt like this in ...



Top 50 recent answers are included