https://bugzilla.novell.com/show_bug.cgi?id=815556 https://bugzilla.novell.com/show_bug.cgi?id=815556#c0 Summary: /etc/zshrc implements very unexpected default zsh-options Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: o.freyermuth@googlemail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 [Open]SUSE's /etc/zshrc sets some zsh-options which are very non-default and as such cause unexpected behaviour and easy data loss, especially for users regularly switching between different distributions. One example which nearly caught me is the setopt globdots contained in there. It leads to "*" matching dotfiles. This is not a default on any major shell and naturally also not on zsh on other distributions for good reason. That's why it stupefies users doing an ls * or even rm -f *, deleting much more than they actually wanted. More ugly examples include deleting all files ending in "*cal" and also deleting .local in the process. As such, workarounds for this [Open]SUSE-specialty have already been created e.g. within GRML (see http://bts.grml.org/grml/issue657 it explicitly sets noglobdots to counteract this unexpected setting). Is there a good reason for these setopt, and if so, why does the system bashrc of [Open]SUSE not set the bash option "dotglob" for consistency at least within the distribution? Otherwise, these lines should be dropped completely to fall back to the wisely-chosen shell-builtin defaults which users expect. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.