Sometimes I get fed up with the high-handedness of systems treating me
"for my own good" like a boisterous three-year-old who must be
protected at all costs from its own curiosity by surrounding him/her
with cotton wool. (And BTW I was a boisterous three-to-five-year-old
myself and I usually found out how to make potentially dangerous
things when my parents weren't looking. Once I tried cutting a live
220V electric wire with steel scissors, and the pain I got as a result
was much more instructive and long-remembered than any "You mustn't do
that, Tony" could have been.)
For instance, in Vim modelines are run in a sandbox which forbids the
most "dangerous" commands, and IMHO this is a good measure; but
(open)SUSE goes farther out by installing behind your back a "system
vimrc" located at /etc/vimrc, one of whose commands goes as follows
(comment included):
" Changed default required by SuSE security team--be aware if
enabling this
" that it potentially can open for malicious users to do harmful things.
set nomodeline
This, IMHO, is going too far, as it removes helpfile highlighting and
doesn't take into account the fact that, even when modelines are
enabled, Vim forbids dangerous commands in a modeline and runs the
rest in a sandbox. In this particular case my answer to this
high-handedness is to compile my own Vim, which looks for its system
vimrc at the Vim default location $VIM/vimrc (which answers "No such
file or directory") rather than at the SuSE default location
/etc/vimrc
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.