Le Sun, 4 Aug 2013 02:11:25 -0300 Maurício Antunes a écrit: > I would like to use dash as an interactive shell. My motivation isn't > anything more serious than the fact that it has a small documentation, > which I can read and understand easily. Maybe my own memory is the limited > resource with which I have to deal :) The problem is that enabling the libedit support does not provide you with auto-completion, AFAIK. This makes it very painful for a use as a daily interactive shell, isn't it? Plus, regarding the documentation, all the shells around claim to comply with POSIX, so you can stick with the dash man page and use another shell, it will work 90% of the time. You can also directly refer to the standard: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/toc.html > My current shell uses tree or > four initialization files, and I can never remember which one is read > when. Dash has only one (.profile). I like that. In fact, dash uses two files: .profile, when you use it as a login shell, and the file pointed in the ENV environment variable, used in all invokations as interactive shell. So, it is the same scheme as bash with .bash_profile and .bashrc. ++ Seb. P-S. I would also like to use dash as my main shell (not just to test script portability). I currently use mksh, which seemed to me a good compromise: smaller and faster than bash, reasonnable auto-completion support, path facilities (e.g. "ls -d /{e,b}*"), a good support for UTF-8, and the ability to deal with many bashisms/kornisms when you really need it: https://www.mirbsd.org/mksh.htm You can also glance the ash in Busybox, which also provides auto-completion, and is a fork of dash. Just build the ash applet to get a ~80K shell: http://www.busybox.net/ -- To unsubscribe from this list: send the line "unsubscribe dash" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html