X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 14 May 2008 09:03:04 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: pdksh package: Error when issuing a 'typeset -r' statement In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <82ba77b80805131833x59a01bb9n246aca58f996b427 AT mail DOT gmail DOT com> X-Google-Sender-Auth: 4a589f418fdbd6b5 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com As a side note, I find modern bash to be a very suitable replacement for ksh. I switched years ago, and I was a heavy Korn Shell user/programmer, a long-time holdout on learning this newfangled "Perl" thing because the KornShell Command and Programming Language was more than sufficient, thankyouverymuch. It follows that my personal ksh environment was heavily customized, so I had to modify it somewhat to make it bash-friendly (main culprits: array syntax, unsupported typeset options, "print", "whence", coprocesses.) It was worth the effort, IMO, since every OS comes with bash these days, while ksh's price tag/license led to slower adoption among open source OSes (and pdksh has never risen to the level of the real thing). I've been quite happy with bash overall, and it might suit your needs as well. -- Mark J. Reed -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/