cygwin zsh problem with FC edit on windows nt

cygwin zsh problem with FC edit on windows nt

Post by jose flanig » Sat, 03 May 2003 01:29:55



I am using the latest cygwin install including zsh version zsh 4.0.6
(i686-pc-cygwin).

Here's the problem. When I do

$ fc -e vi 14

to edit history line 14, I get the following error upon exiting

zsh: read error on /tmp/zsh001043

I checked all the permissions on the drive /tmp and they are correct.
I observe the file zsh001043 being created okay so I don't know what
the problem is.

help!

Thanks in advance.

 
 
 

cygwin zsh problem with FC edit on windows nt

Post by Pavol Juh » Sat, 03 May 2003 05:26:47



Quote:> I am using the latest cygwin install including zsh version zsh 4.0.6
> (i686-pc-cygwin).

> Here's the problem. When I do

> $ fc -e vi 14

> to edit history line 14, I get the following error upon exiting

> zsh: read error on /tmp/zsh001043

> I checked all the permissions on the drive /tmp and they are correct.
> I observe the file zsh001043 being created okay so I don't know what
> the problem is.

The same happens to me (zsh 4.0.6) when /tmp/zsh001043 becomes
empty.  Try to save that file with a single <space> character.
If that really bothers you, you may try:

function vi4fc () { vi $1; [[ -s $1 ]] || echo >> $1 }
fc -e vi4fc 14

I wonder if that error message is a bug or feature.

HTH,

Pavol

 
 
 

cygwin zsh problem with FC edit on windows nt

Post by jose flanig » Sat, 03 May 2003 21:56:46


Thanks for your suggestion. The problem is that the fc-edited command
is NOT executed AND the 'read error' message is reported.  I could
live w/ the complaint so long as the fc-edited command was executed.

Also, I'm not sure what you mean in your post by "Try to save that
file with a single <space> character". I tried the function vi4fc that
you defined but I still have the same problem.

Any other suggestions? Thanks for your help.

Jose



> > I am using the latest cygwin install including zsh version zsh 4.0.6
> > (i686-pc-cygwin).

> > Here's the problem. When I do

> > $ fc -e vi 14

> > to edit history line 14, I get the following error upon exiting

> > zsh: read error on /tmp/zsh001043

> > I checked all the permissions on the drive /tmp and they are correct.
> > I observe the file zsh001043 being created okay so I don't know what
> > the problem is.

> The same happens to me (zsh 4.0.6) when /tmp/zsh001043 becomes
> empty.  Try to save that file with a single <space> character.
> If that really bothers you, you may try:

> function vi4fc () { vi $1; [[ -s $1 ]] || echo >> $1 }
> fc -e vi4fc 14

> I wonder if that error message is a bug or feature.

> HTH,

> Pavol

 
 
 

cygwin zsh problem with FC edit on windows nt

Post by Pavol Juh » Sun, 04 May 2003 01:37:51




> > > I am using the latest cygwin install including zsh version zsh 4.0.6
> > > (i686-pc-cygwin).

> > > Here's the problem. When I do

> > > $ fc -e vi 14

> > > to edit history line 14, I get the following error upon exiting

> > > zsh: read error on /tmp/zsh001043
...
> > The same happens to me (zsh 4.0.6) when /tmp/zsh001043 becomes
> > empty.  Try to save that file with a single <space> character.
> > If that really bothers you, you may try:

> > function vi4fc () { vi $1; [[ -s $1 ]] || echo >> $1 }
> > fc -e vi4fc 14

> Thanks for your suggestion. The problem is that the fc-edited command
> is NOT executed AND the 'read error' message is reported.  I could
> live w/ the complaint so long as the fc-edited command was executed.

> Also, I'm not sure what you mean in your post by "Try to save that
> file with a single <space> character". I tried the function vi4fc that
> you defined but I still have the same problem.

I see.  I have no problem to execute the commands.  I am getting that
message only, when I delete all of the command line in vi,
i.e. when the saved file becomes empty.  The vi4fc function
only ensures that the file contains at least 1 character (1 line
feed).

Quote:> Any other suggestions? Thanks for your help.

May be there are some strange settings, which cause this problem.
Try to run  zsh -fx  and see what happens.  The option -f
(NO_RCS) tells zsh to ignore all initialization files except
/etc/zshenv; -x turns on XTRACE, which tells zsh to
print everything what is done.

Also, are you using cygwin version of vi/vim?  Note, that in
cygwin /tmp is in fact c:\cygwin\tmp, or something
similar (see the output of mount).  If you call windows version of
vi/vim, it would edit c:\tmp\zsh001043.  On my cygwin I have
mounted /tmp to c:\tmp, so I can use the same tmp path
(/tmp or \tmp) in all programs.

HTH,

Pavol

 
 
 

1. CYGWIN zsh problem

Hi all,

I've just recently installed cygwin on my XP box, and I am having
troubles getting  the 'z' shell to work. Whenever I execute any
commands through it, the output becomes corrupted with random
characters appended onto the end. They look like this:

\[\033]0;\w\007

Does anybody know how I can rid of this?

Steve.

2. Printing to an SMB Winprinter

3. UNIX (Cygwin 32) programming on Windows NT

4. Is E6900 == SF6900? Application(SF6800) -->Application(SF6900) ??

5. How to set color of zsh in Windows NT.

6. LILO no kernel, no lilo.conf, reboot cycle.

7. Zsh for Windows NT?

8. can't find commands

9. ZSH: How to setup startup files on windows NT

10. ksh problem: fc doesn't execute edited command

11. double slash in path (Cygwin & zsh)

12. NT NT NT NT NT NT NT MT

13. zsh on NT problems.