Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Heading says it all really. Using Windows 7 and latest stable gvim, whenever I save (:w) a file it’s marked executable. I’m doing cross-platform development and it’d be nice if this didn’t happen.
@sceptics: The flag of the files are indeed set as executable. Do a
ls -albefore and after re-saving the file to observe the issue. (install cygwin, or may be other *nix emulations)@OP: the question have been raised several times in the past. I don’t remember the conclusion on the subject. You should search vim mailing-lists archives (vim_use and vim_dev).
May be you can try to add an hook to your RCS (if it supports that) to proceed to a
chmod -xon file extensions that does not correspond to an executable (*.h, *.cpp, *.vim, …), or on files that do not contain a shebang (unlike perl, I don’t know if python source files may contain a shebang)