CaffeineAddict
Well-Known Member
So it's the same thing as ensuring that bash is in PATH so that it can be found?I agree it slows things down. But at least it usually finds it.![]()
So it's the same thing as ensuring that bash is in PATH so that it can be found?I agree it slows things down. But at least it usually finds it.![]()
I knew that one existed but none like these:bash already does those things by default. I have noticed some distro do have an auto-complete plugin for bash.
zsh-history-substring-search
zsh-syntax-highlighting
Fish shell has these out of the box but doesn't play well with bash.zsh-history-substring-search zsh-syntax-highlightingI have looked for them in the past for bash and because I couldn't find anything like them I switched to zsh at some point.
See: https://wiki.debian.org/ShellThe default non-interactive shell on POSIX environments is an executable located on the filesystem at /bin/sh, which is a symbolic link to the default shell. Most system scripts use this, via the #!/bin/sh shebang. Changing a system's default non-interactive shell is simply a matter of changing that symbolic link to target a different executable.
In all releases up to and including DebianLenny, Bash was the default non-interactive shell. Beginning with DebianSqueeze, Debian uses Dash (the Debian Almquist shell) as the target of the /bin/sh symlink. Dash lacks many of the features one would expect in an interactive shell, which allows it to be faster and more memory efficient than Bash.
See: https://zsh.sourceforge.io/Doc/zsh_a4.pdfIt does not provide compatibility with POSIX or other shells in its default operating mode.
Change the behavior of bash where the default operation differs from the POSIX standard to match the standard (posix mode)