Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #273067
| From | Will Mengarini <seldon@eskimo.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: unwanted crontab message |
| Date | 2024-09-14 00:50 +0200 |
| Message-ID | <JmngZ-c4IA-5@gated-at.bofh.it> (permalink) |
| References | <JmmkV-c47r-1@gated-at.bofh.it> <JmmuB-c4du-11@gated-at.bofh.it> <JmmNX-c4za-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
You are getting Vim error messages from a version of Vim that does not support scripting (probably vim.tiny). That version is probably installed on your system ALONG WITH a version that does support scripting, but cron does not have the scripting version of Vim on PATH. (Typically, your $HOME & root PATHs are more elaborate than the one to which cron defaults.) The solution is to set PATH in your crontab. * Marcus Park <marp@privatembox.com> [24-09/14=Sat 06:12 +0800]: > > Andy Smith : >> As to why whatever it is set as right now is doing that, first work >> out where it is getting the setting from, so echo $EDITOR and echo >> $VISUAL. If neither of those are set then ls -la /usr/bin/editor. > > Thanks Andy. > > either $EDITOR or $VISUAL in my system is empty. > > And /usr/bin/editor points to nano. > > Then I run this command, > > $ sudo update-alternatives --config editor > There are 4 choices for the alternative editor (providing /usr/bin/editor). > > Selection Path Priority Status > ------------------------------------------------------------ > * 0 /bin/nano 40 auto mode > 1 /bin/ed -100 manual mode > 2 /bin/nano 40 manual mode > 3 /usr/bin/vim.basic 30 manual mode > 4 /usr/bin/vim.tiny 15 manual mode > > Press <enter> to keep the current choice[*], or type selection number: 3 > update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/editor > (editor) in manual mode > > > > to choose vim.basic as default editor. > > In my system both vim.basic and vim are the same stuff, > > $ vim --version > VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 27 2024 05:34:22) > Included patches: 1-16, 647, 17-579, 1969, 580-647, 678, 648-1848, 4975, > 5016, 5023, 5072, 2068, 1849-1854, 1857, 1855-1857, 1331, 1858, 1858-1859, > 1873, 1860-1969, 1992, 1970-1992, 2010, 1993-2068, 2106, 2069-2106, 2108, > 2107-2109, 2109-3995, 4563, 4646, 4774, 4895, 4899, 4901, 4919, 213, 1840, > 1846-1847, 2110-2112, 2121 > ... > > > $ vim.basic --version > VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 27 2024 05:34:22) > Included patches: 1-16, 647, 17-579, 1969, 580-647, 678, 648-1848, 4975, > 5016, 5023, 5072, 2068, 1849-1854, 1857, 1855-1857, 1331, 1858, 1858-1859, > 1873, 1860-1969, 1992, 1970-1992, 2010, 1993-2068, 2106, 2069-2106, 2108, > 2107-2109, 2109-3995, 4563, 4646, 4774, 4895, 4899, 4901, 4919, 213, 1840, > 1846-1847, 2110-2112, 2121 > ... > > > Then I logged out and re-login the system, run 'crontab -e', the error still > shows. Maybe I got bad luck today. :( > > Regards.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
unwanted crontab message Marcus Park <marp@privatembox.com> - 2024-09-13 23:50 +0200
Re: unwanted crontab message Andy Smith <andy@strugglers.net> - 2024-09-14 00:00 +0200
Re: unwanted crontab message Marcus Park <marp@privatembox.com> - 2024-09-14 00:20 +0200
Re: unwanted crontab message Will Mengarini <seldon@eskimo.com> - 2024-09-14 00:50 +0200
Re: unwanted crontab message Will Mengarini <seldon@eskimo.com> - 2024-09-14 01:00 +0200
Re: unwanted crontab message Andy Smith <andy@strugglers.net> - 2024-09-14 00:50 +0200
Re: unwanted crontab message Greg Wooledge <greg@wooledge.org> - 2024-09-14 03:00 +0200
Re: unwanted crontab message Greg Wooledge <greg@wooledge.org> - 2024-09-14 00:00 +0200
Re: unwanted crontab message Michael Kjörling <c9bc136c6063@ewoof.net> - 2024-09-14 10:50 +0200
csiph-web