Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Feb 2002 14:46:34 -0600
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Dan Langille <dan@langille.org>
Cc:        Matt of the Long Red Hair <mattp@conundrum.com>, questions@FreeBSD.ORG
Subject:   Re: crontab entries need a CR/LF at the end
Message-ID:  <20020214204634.GA89093@dan.emsphone.com>
In-Reply-To: <200202142026.g1EKQUk28938@lists.unixathome.org>
References:  <20020214145934.Y46360-100000@bsd.smnolde.com> <200202142026.g1EKQUk28938@lists.unixathome.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Feb 14), Dan Langille said:
> On 14 Feb 2002 at 15:17, Matt of the Long Red Hair wrote:
> 
> > I managed to reproduce this user's problem, but I had to work at it. 
> > Simply editing the file with a text editor won't do it, since most leave a
> > \n at the end of even the last line.  I had to do this:
> > 
> > % echo -n "* * * * * ls ~/bin" > crontab
> > % crontab crontab
> 
> FWIW, I was using joe
> 
> > I'm not sure if this is a bug or not, but his observations are at least
> > valid. It seems bug-like to me, though probably not a very high priority
> > one.
> 
> Thank you.  And agreed, definintely low-priority.

You can adjust joe's behaviour by removing the leading space from this
line in your joerc:

 -force     Force final newline when files are saved



-- 
	Dan Nelson
	dnelson@allantgroup.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020214204634.GA89093>