Re: unwanted crontab message

2024-09-14 Thread Michael Kjörling
On 13 Sep 2024 17:53 -0400, from g...@wooledge.org (Greg Wooledge): > For the record, Debian 12 has vim 9.0.x and a /usr/share/vim/vim90/ > directory. According to ... oh, > that web page is not responding for me. Sorry, I can't check what > version(s) of Debian m

Re: unwanted crontab message

2024-09-13 Thread Greg Wooledge
On Fri, Sep 13, 2024 at 22:46:09 +, Andy Smith wrote: > I just ran crontab -e as a fresh user and it actually invoked > /usr/bin/sensible-editor and asked me which editor I wanted to use > (now and in future). So perhaps the man page for crontab is out of > date. Agreed. hobbit:~$ strings /us

Re: unwanted crontab message

2024-09-13 Thread Will Mengarini
Or ... disambiguate which Vim crontab -e is using, so it's not vim.tiny. * Will Mengarini [24-09/13=Fri 15:47 -0700]: > 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

Re: unwanted crontab message

2024-09-13 Thread Will Mengarini
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 & ro

Re: unwanted crontab message

2024-09-13 Thread Andy Smith
Hi, On Sat, Sep 14, 2024 at 06:12:02AM +0800, Marcus Park wrote: > either $EDITOR or $VISUAL in my system is empty. > > And /usr/bin/editor points to nano. Well, I do not really understand what is going on then as you are definitely running an editor that looks at vim config files, and nano won'

Re: unwanted crontab message

2024-09-13 Thread Marcus Park
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/

Re: unwanted crontab message

2024-09-13 Thread Andy Smith
Hi, On Sat, Sep 14, 2024 at 05:44:42AM +0800, Marcus Park wrote: > When I run 'crontab -e' the screen shows some errors like, > > $ crontab -e > Error detected while processing /usr/share/vim/vim82/filetype.vim: I'm pretty sure that these errors will be coming from the editor binary that is set

Re: unwanted crontab message

2024-09-13 Thread Greg Wooledge
On Sat, Sep 14, 2024 at 05:44:42 +0800, Marcus Park wrote: > Hi list, > > When I run 'crontab -e' the screen shows some errors like, > > $ crontab -e > Error detected while processing /usr/share/vim/vim82/filetype.vim: > line 10: > E319: Sorry, the command is not available in this version: let

unwanted crontab message

2024-09-13 Thread Marcus Park
Hi list, When I run 'crontab -e' the screen shows some errors like, $ crontab -e Error detected while processing /usr/share/vim/vim82/filetype.vim: line 10: E319: Sorry, the command is not available in this version: let did_load_filetypes = 1 line 13: E319: Sorry, the command is not availa