Re: cron on 10.5.2 server

In article <682cq3F2qi61hU1@[EMAIL PROTECTED]
>,
 Chris Ridd <chrisridd@[EMAIL PROTECTED]
> wrote:

> On 2008-05-03 06:48:49 +0100, Jolly Roger <jollyroger@[EMAIL PROTECTED]
> said:
> 
> > In article <682brbF2rihq4U1@[EMAIL PROTECTED]
>,
> >  Chris Ridd <chrisridd@[EMAIL PROTECTED]
> wrote:
> > 
> >>> I'm not so sure you really can use a GUI editor to edit cron tables.
I
> >>> just tried with EDITOR set to TextWrangler's 'edit' command-line
tool,
> >>> and it exited immediately with:
> >>> 
> >>> ex****t EDITOR=/usr/bin/edit
> >>> # echo $EDITOR
> >>> /usr/bin/edit
> >>> # crontab -e
> >>> crontab: no changes made to crontab
> >> 
> >> The man page for edit talks about how to make crontab run it
properly,
> >> and how to make other Unix tools run it via $EDITOR.
> > 
> > Thanks - I hadn't bothered to read the man page, because vim suits my
> > needs perfectly, so I've never bothered to switch my editor.
> 
> I wonder if the bug in crontab alluded to at the end is still present?

My take is that's not a bug, but is just the way it is, because of the 
way crontab parses the EDITOR environment variable.

-- 
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR