From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JDRcl-0007o6-UU for garchives@archives.gentoo.org; Fri, 11 Jan 2008 21:41:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4472AE0BAE; Fri, 11 Jan 2008 21:40:44 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 7C0D5E0BA2 for ; Fri, 11 Jan 2008 21:40:43 +0000 (UTC) Received: from buddha (ppp-88-217-77-35.dynamic.mnet-online.de [88.217.77.35]) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis) id 0ML21M-1JDRcI1xz4-0006GL; Fri, 11 Jan 2008 22:40:42 +0100 Date: Fri, 11 Jan 2008 22:41:37 +0100 From: "Matthias B." To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: emerge of ksh93 erroring out.. who can interpret Message-ID: <20080111224137.37cf5ba4@buddha> In-Reply-To: <87ejco42es.fsf@newsguy.com> References: <200801081139.54044.alan.mckinnon@gmail.com> <87y7azranl.fsf@newsguy.com> <20080110203452.776ded95@buddha> <87hchk5lhn.fsf@newsguy.com> <20080111192643.37761ba2@buddha> <87ejco42es.fsf@newsguy.com> X-Mailer: Sylpheed-Claws 1.0.4 (GTK+ 1.2.10; i586-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19IgYOLkaDOrQ6B1yxfb+DuIzurju2cmamNq27 cmpsEZEeE7UF0GK09mak22A0RCN0G6JbfjJQyMKj2BNNJeLr3k hR9j/WrXKlqgiDvY+2kI3NoYEo9bCCS X-Archives-Salt: 749f5075-e246-4f57-889b-932945732cf0 X-Archives-Hash: 3a8bd56380138642be5c7f3cec2277b5 On Fri, 11 Jan 2008 12:56:11 -0600 reader@newsguy.com wrote: > Can you cite some actual examples of what you are talking about, with > enough detail so I can see what you mean? Maybe include one or two of > the workarounds you are tired of dealing with? One thing I encountered is this bug > echo "$(echo $';foo')" bash: foo: command not found introduced with some 3.1 version. Then at some point the following stopped working for d in `echo $locdirs | sed -e 's#/# #g'`; do because bash stupidly regarded the embedded # as comment delimters and complained about not finding the closing backtick. Both bugs are fixed now. Both cases broke scripts that I had released as part of a project and therefore caused bug reports against my script. There were others but I don't have the time to dig them out. I'm not trying to convince you to stay away from bash, just telling you my reasons. Oh, I forgot to mention that I found the zsh developers much easier to get in touch with and much more responsive about bug reports. But all of this is off-topic for gentoo-user, so I'll stop now. MSB -- The biggest fallacy of the SETI project is the belief that TV signals are a sign of intelligence! -- gentoo-user@lists.gentoo.org mailing list