>Erm, the same will happen if we update shells like "bash" which enable >some switches/features by default. And you even have the reverse problem >- for example with ksh93: ksh93 does not enable any flags by default as >required by the POSIX shell standard. Unfortunately this is bad for >usuablity (e..g no working cursor keys or history - if you think this is >acceptable go to the ksh93-integration archives and read the postings >about TAB-TAB, history etc (AFAIK a few hundred postings just about >these "little usability things")) and that's why we had an extra ARC >case (PSARC 2006/587) to populate /etc/ksh.kshrc and enable the "gmacs" >editor mode there to match the requests by the community.
Upgrades of binaries which radically change behaviour is a problem. We've not allowed that in the past but we are allowing that now, albeit with some qualms (and being on the receiving end is never fun; the continuous retraining with netscape/mozilla/firefox is not a fun experience; whenever one thing improves another thing invariably gets worse, like the hokey per-tab closeboxes) So we're going down that path some; I'm not sure we should go down that path even further, especially when there are reasonable alternatives. >Or short: This ARC case (which proposes to ses PS1) is just an extension >of PSARC 2006/587, following the precedent made there. Can you give me the invocation of "kshelless" with sets the prompt back to "$ " or "# " respecitively? >I am not sure for /etc/profile but /etc/ksh.kshrc and /etc/bash.bashrc >are for interactive shells _only_ and the setting of PS1 and the editor >are local shell variables/settings which are not exported into the >environment (e.g. process children won't get the changes unless you do >something like $ export PS1 #). /etc/profile is for login shells; there's no way to run anything specifically for an interactive "Bourne" shell. (I may be confusing my cases here, but since all cases are intertwined it's perhaps an idea to merge the default settings cases in one) Casper
