🚀 go-pugleaf

This seems odd. Just a suggestion.  Try execing bash first (exec bash),
then setting EDITOR to the PATH of the new emacs and make sure EDITOR is
not pointing to a symbolic link. While symbolic links should be totally
transparent to a process that opens a file I have run into problems with
apache where replacing a symbolic link with the actual target fixed my
problems (and yes it should not work this way). 

The other option if this is your own system is to login as root and
change directory to /var/spool/cron.  You can always create/edit your
crontab file as root (name it according to your user id); the crontab
command is a convenience so to get around the directory permissions for
/var/spool/cron.

Stan

Adam wrote:
> 
> I'm running Mandrake 8.1, which came with Emacs 20.7. I'm not familiar with
> vi, so I put these lines in my normal .bashrc and my root .bashrc:
> 
> # default editor, e.g. for crontab
> EDITOR='/usr/bin/emacs'
> export EDITOR
> 
> That worked; crontab -e used to bring up Emacs and modify the crontab. A
> few days ago I upgraded to Emacs 21.1.1. I changed /usr/bin/emacs to point
> to the new version and my scripts that use it work correctly.
> 
> But crontab no longer works correctly:
> 
> /home/adam $ crontab -e
>   (over in the Emacs window: made changes, C-x C-s C-x C-c)
> crontab: no changes made to crontab
> /home/adam $
> 
> Interestly crontab -l worked and crontab -r worked, so I now have an empty
> crontab, which I can't change:
> 
> /home/adam $ crontab -e
> no crontab for adam - using an empty one
>   (over in the Emacs window: made changes, C-x C-s C-x C-c)
> crontab: no changes made to crontab
> /home/adam $
> 
> The cron daemon is still working correctly, since root's cron jobs are
> still running correctly.
> 
> Any ideas?
> 
> Thanks
> Adam