I don't think its my use of vi, it could be though, when in Insert/Append
(Shift+I or A) mode isnt Ctrl+C (break or ^C) the standard way of getting
back to the state whereby I can issue :wq ?

vi has never done something like this and I frequently use the above
described method for editing files (presing ^C to get back to the command
mode when in Insert/Append).

Thomas M Clarke

(sorry for replying directly to you Harry Waddell, my mistake)

----- Original Message -----
From: "Harry Waddell" <waddell@caravan.com>
To: "Joe Reed" <jnr@cwru.edu>
Cc: <tmc@tmcgames.com>; <netbsd-help@netbsd.org>
Sent: Monday, February 24, 2003 11:07 PM
Subject: Re: crontab I/O Error


> On Mon, 24 Feb 2003 17:41:16 -0500
> Joe Reed <jnr@cwru.edu> wrote:
>
> > do you get the error if you add some text and then properly save and
close
> > vi??  (which is what you need to do to edit your crontab properly)
>
> crontab looks at the EDITOR env variable. So you can edit your
> crontab with whatever you like. So, if you're vi challenged, try something
> else, e.g. using /bin/sh syntax
>
> EDITOR=emacs crontab -e
>
>
> >
> > ... synopsis of what i do...
> > $ crontab -e
> > ..add/modifiy/delete my crontab rules
> > [esc] :wq [enter] ...(standard vi save and close)...
> > ...end synopsis..
> > --joe
> >
> > On Monday 24 February 2003 11:09 am, Thomas M Clarke wrote:
> > > Hello Everyone,
> > >
> > > As root I'm trying to edit my crontab, I issue the crontab -e command
> > > and it brings up a vi session with my crontab. If I add any text to
this
> > > file and ^C it immediately throws a wobbly and complains of: ERROR:
> > > Input/Output Error and bombs out of vi back to the prompt. Any ideas
of
> > > what I can try to get this working?
> > >
> > > Thanks
> > >
> > > Thomas M Clarke
>
>
> --
> Harry Waddell
> Caravan Electronic Publishing
> -----------