Re: cron on 10.5.2 server

In article <nospam.News.Bob-EE7E05.18430925042008@[EMAIL PROTECTED]
>,
 Bob Harris <nospam.News.Bob@[EMAIL PROTECTED]
> wrote:

> In article <bob-E4827D.22442724042008@[EMAIL PROTECTED]
>,
>  Robert Peirce <bob@[EMAIL PROTECTED]
> wrote:
> 
> > In article <nospam.News.Bob-FC333A.21423324042008@[EMAIL PROTECTED]
>,
> >  Bob Harris <nospam.News.Bob@[EMAIL PROTECTED]
> wrote:
> > 
> > > OK, some suggestions:
> > > 
> > > 1)  Modify your own .vimrc to specify your own nowritebackup
> > > 
> > >     autocmd BufReadPre,FileReadPre crontab.* set nowritebackup
> > > 
> > >     NOTE 1: I am setting the value when the file is read,
> > >             NOT when it is written.
> > > 
> > >     NOTE 2: I did NOT specify a directory path.
> > >             I just said any file that starts with
> > >             crontab.* is treated this way.
> > > 
> > > 2)  Make the above modification to /usr/share/vim/vimrc
> > 
> > This works!  Thanks, so much.  I tried it first in my own .vimrc file 
> > then I put it in the system file.
> > 
> > I have been reviewing the vim help on "events."  Actually seeing this 
> > really helped a lot.
> > 
> > Now I am wondering why BufReadPre and FileReadPre work but BufWrite
does 
> > not.  BufWrite is supposed to apply before writing, but there must be 
> > some kind of delay operating that is preventing this. Anyhow, you got
it 
> > working for me and I appreciate it.
> 
> /usr/share/vim/vimrc specified /private/tmp/crontab.*, however, 
> when I was doing my testing, I noticed that Vim thought the file 
> was stored in /tmp/crontab.*
> 
> I am assuming that the real root of the problem is that they 
> changed the behavior of crontab -e to use a different path for the 
> file being edited.  But no one thought to fix the 
> /usr/share/vim/vimrc file.

I had /private/tmp linked to /tmp.  I picked that up in 10.4.  I ran 
into a problem with some other program that had the same situation.  Now 
I can't remember what it was.  I guess I didn't realize I was also 
fixing cron!

More im****tantly, I got the original version of vimrc to work.  I first 
tried your idea of removing the path and that worked.  Then I put the 
path back in and it worked.  The only thing I can figure is I must have 
had an unprintable character buried somewhere in the path and it got 
removed when I was playing with it.

I really appreciate everybody's help.  It looks like everything is back 
together and working the way it is supposed to work.

-- 
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]