SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is kind of a strange one that I've noticed before but haven't bothered to post until now. On Slackware64-14.2, when I do this:
Code:
EDITOR=/usr/bin/vim crontab -e
The crontab file is opened in vim as expected. However, when I make changes, save, and view the crontab again, it is apparent that the changes were not actually saved. The issue does not occur with other editors. Can anyone confirm?
I never use vim, but gave it a try now...
Changed the default hourly cron jobs 47 min to 45 min and saved/exit.
Reopening the file and the changes are still there...
This is kind of a strange one that I've noticed before but haven't bothered to post until now. On Slackware64-14.2, when I do this:
Code:
EDITOR=/usr/bin/vim crontab -e
The crontab file is opened in vim as expected. However, when I make changes, save, and view the crontab again, it is apparent that the changes were not actually saved. The issue does not occur with other editors. Can anyone confirm?
Vim has these lines in /usr/share/vim/vimrc :
Code:
" Make vim work with the 'crontab -e' command
set backupskip+=/var/spool/cron/*
It could be that you somehow have an older version of that file where the backupskip line is not present (as was the case in older versions of Slackware).
" Make vim work with the 'crontab -e' command
set backupskip+=/var/spool/cron/*
It could be that you somehow have an older version of that file where the backupskip line is not present (as was the case in older versions of Slackware).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.