> On 12. Jan 2025, at 21:59, Andrej Shadura <andre...@debian.org> wrote: > > At least in Debian, dash is primarily a shell for scripts, not for > interactive use. (That’s also why we don’t enable libedit.) > So some escape sequences not being available in the prompt are not of a huge > concern for us. > I think the same can be said about HISTCONTROL.
I’m not trying to tell you that Debian is doing anything wrong, but rather explaining why we need these features. Apparently, a number of Debian users think it’s a good idea to use dash as a login shell. Generally, we try to support all subshells at least to some minimal degree. Then they discover that our internal shell communication clobbers their history, and the prompt is not displayed correctly. The prompt issue can be resolved if we can tell Dash apart from Busybox ASH, but we can’t do anything about the history thing unless Dash implements something that would allow certain commands to be left out of the history file… So our answer for now is to suggest using another shell and fixing the prompt by telling ash-es apart from each other. All the best, Yury
