This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Using $EDITOR (Was Re: [ANNOUNCEMENT] Updated: cron-3.0.1-9)
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Ehud Karni <ehud at unix dot mvs dot co dot il>
- Cc: cygwin at cygwin dot com, <lucianoav at gmx dot net>
- Date: Mon, 21 Apr 2003 00:51:47 -0400 (EDT)
- Subject: Re: Using $EDITOR (Was Re: [ANNOUNCEMENT] Updated: cron-3.0.1-9)
- Reply-to: cygwin at cygwin dot com
On Sun, 20 Apr 2003, Ehud Karni wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 16 Apr 2003 21:37:28 -0400 (EDT), Igor Pechtchanski <pechtcha at cs dot nyu dot edu> wrote:
> >
> > Yes, you can do that. That way programs like crontab will invoke your
> > editor when they need to edit a file. However, be aware that such
> > programs often expect certain behavior, for example, that the inode of the
> > file doesn't change when it's edited (i.e., the file is written in place).
>
> This can be easily done with a script (use its name for $EDITOR):
>
> #!/bin/sh
> cp $1 /temp/crontab/name # copy to a temp file
> <YOUR_EDITOR> /temp/crontab/name # edit it (e.g. with emacs)
> cat /temp/crontab/name > $1 # save as original file (and inode)
>
> Ehud.
Ehud,
Actually, you might want to use "cp -p", just in case the editor checks
timestamps, but otherwise, good point. You might also have to clean up if
the editor renames the original file to *.bak or something, but this is
editor-specific. You also will need the "ash" package installed for this
(trivial, but thought I'd mention it for the archives anyway).
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Knowledge is an unending adventure at the edge of uncertainty.
-- Leto II
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/