This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: zsh-4.2.0-2
On Thu, 8 Apr 2004, zzapper wrote:
> On Wed, 7 Apr 2004 11:20:41 -0400 (EDT), wrote:
>
> >- Fix for running scripts from text-mode mounted filesystems. Previously
> > if you ran a script from a text-mode mount, and it had DOS CR/LF's line
> > termination, zsh would report ^M errors. The shell now opens such
> > files with O_TEXT which causes line termination to be massaged. I'll
> > be watching for problem reports concerning this as it was a broad
> > change, the implications of which haven't been fully realized yet.
>
> Peter your new version of zsh solved my ^M errors thanx.
Well, since you were the one who spoke up and said there was a problem,
I'm happy it makes things better for you. It's something that's been on
my back-burner for a while, and decided it was time to dig into it. Do
let me know if you have any other problems related to this. That goes
for everyone else, too.
> But why did I have to manually copy /bin/zsh-4.2.0 to /bin/zsh.exe to
> get the update (tried doing a ln with no luck)? What do I have to
> change in my config?
*grumble* Hmm... I suspect this is really a Setup issue. The binary is
stored in the tar as a hardlink to the versioned name. If you manually
unpack it, with tar, it does the right thing. On an NTFS volume, it
makes it a hardlink to the real file (ie: link count = 2). On a FAT
volume, it duplicates the file's contents (ie: link count = 1). It
appears setup isn't quite handling it correctly for your configuration.
We'd have to get detailed info about your config. Are you using the
latest setup.exe, btw? If not, try a snap-shot first. It's as simple a
un-installing and re-install zsh to test.
Just as a test, could you do the following? In a empty dir, unpack the
binar archive. eg:
$ mkdir /tmp/testzsh
$ cd /tmp/testzsh
$ tar -xjvf /path/to/zsh-4.2.0-2.tar.bz2 > untar.out 2>&1
$ ls -al usr/bin >> untar.out
This will capture the output of tar unpacking (in case there's a problem)
as well as shows what files were unpacked in usr/bin. If you could send
me untar.out, it might shed some light on the matter. A copy of the
/var/log/setup.log{.full} might be good too after a re-install of just
zsh. And, while we're at it, the standard "cygcheck -s -v -r" output
might prove insightful.
> zzapper (vim, cygwin, wiki & zsh)
--
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
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/