Among these and others I omitted:
- esAUR - Wikipedia says "Stable release 0.9-beta1 (1997)" so I do not trust this one.
pshAUR - Not sure what this actually is, if it is usable, etc. sashAUR - Does not have a proper home page nor that much documentation so I do not trust this one.
- busybox shell - It is a recovery interface, pretty difficult. But maybe a mention is worth...
- heirloom - Good only for a museum apparently :)
- dosbox - Does this suit the category?
- python/ipython. - Does this suit?
Any suggestion? -- Flu (talk) 17:37, 31 August 2013 (UTC) Edited -- Flu (talk) 21:19, 5 September 2013 (UTC)
- I'd only include shells which actually prove useful, instead of making the page an AUR (or otherwise) dump. Others can stay on the talk page, I suppose. -- Alad (talk) 12:41, 8 August 2014 (UTC)
May move a section from Bash eventually
I think that Bash#Configuration could be moved here, making a comparison table of configuration files, how to define aliases and functions and maybe more. -- Flu (talk) 21:19, 5 September 2013 (UTC)
Since there is an "Alternative sells" section, there is a number of high-quality untraditional shells that are usable and used.
- eshell, POSIX-like, but not compatible (AFAIK). Eshell is built from Emacs Lisp functions and it is able to fully integrate into Emacs, it is different from all other shells - it allows to treat shell OI complexly as a textual Emacs buffer, allows to edit/work with it as text buffer. I do not use it, but I am constantly surprised at how many people go into a deep end of Emacs, so mentioning it seems logical. Of course one can use eshell even without explicitly launching it in Emacs, it can be used for a script, or run as a shell inside a terminal.
- nushellAUR - it is non-compatible shell, but really interesting and futuristic in design comparing for what today is in use, it provides a more unified CLI UI and a set of tools and features, more reassembling a Cisco IOS shell then POSIX Linux shell. It is object-oriented shell, modular. Anton Latukha (talk) 11:54, 10 August 2020 (UTC)
Out of date link in Command-line_shell#Standardisation
This section includes 2 links. The link to "the related repository" https://bitbucket.org/flowblok/shell-startup now leads to a repository unavailable message. The related article https://blog.flowblok.id.au/2013-02/shell-startup-scripts.html is useful for the diagrams on what config files are called when, but doesn't seem to describe how to make the shells follow a given naming convention. I'm assuming that was intended to be learned by looking at the repo. With it missing, I'm not sure how much value this whole section has currently. -- Madasi (talk) 23:19, 26 August 2020 (UTC)
- Feel free to flag the section with an appropriate article status template. – Lahwaacz (talk) 20:16, 27 August 2020 (UTC)