To: cygwin@cygwin.com
From: Paul Mead <paul.d.mead@gmail.com>
Subject:  Re: Trouble creating crontab
Date:  Fri, 17 Jul 2009 08:34:53 +0100
Lines: 25
Message-ID:  <87bpnjyd7m.fsf@gmail.com>
References:  <87skgwy4rb.fsf@gmail.com> <4A5F5A73.1070708@cygwin.com> 	<87ocrky34v.fsf@gmail.com> <4A5F5EDD.4080001@cygwin.com> 	<87k528y1nb.fsf@gmail.com> <slrnh5v7vl.1bph.oudeis@isis.thalatta.eme> 	<20090716215248.GA28657@ednor.casa.cgf.cx> 	<slrnh5v9g9.1bph.oudeis@isis.thalatta.eme>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.96 (windows-nt)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Will Parsons <oudeis@nodomain.invalid> writes:

>>>>Is there no way of just creating the file without using crontab -e?
>>>
>>>Sure.  I've been editing crontabs for years and have never once used
>>>crontab -e.  What I do:
>>>
>>>crontab -l > crontab.lst edit crontab.lst crontab crontab.lst
>>
>> I always just use the toggle switches on the front panel of my computer.
>>
>> Much easier.
>
> Was that really necessary?  The procedure I use may very well be easier
> than figuring out the right thing to do to invoke one's editor of choice
> with the -e option.  In my case, I prefer to explicitly to export the
> crontab table into a file so that I can put it into revision control.  At
> any rate, answering an explicit question from the OP hardly deserves a
> display of sarcasm.

I for one burst out laughing when I saw the response, no offense
taken. I'll use the advice to export the file for editing, thanks for
that. No need to worry about sarcasm on my account, the response kind of
summed up some of the more esoteric areas that I'm coming across with my
*nix / cygwin learning...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple