* J.Z. <[email protected]> [120110 19:43]: > thanks, set ft=sh did the trick. I cannot use.sh extension for files > for ksh funtions, and cannot have #! in them also.
(Please do not top-post.) I'm curious why you can't use a shebang line (#!) in ksh. I haven't used ksh since the early '90s, but a quick test here seems to work fine. I installed ksh and created the following simple ksh script named ksh-test: ----- #!/usr/bin/ksh echo $KSH_VERSION ----- Typing ksh-test at a bash prompt executed it properly and gave Version JM 93u 2011-02-08 which is evidence that the shebang line was properly parsed. I also invoked ksh and did the same from a ksh prompt, with the same result. Editing the file with vim and with gvim both recognize the filetype as sh as expected. Are you not allowed to use #! because of some corporate coding policy, or is there some technical reason that the shebang interferes with some special way you are processing the scripts? I'm just curious, because in general, using a #! is the "right" way to do this. It both allows the editor to determine the correct file type and allows the OS to invoke the script with the correct interpreter. It also makes it clear to a person reading the script for which shell it is intended. ...Marvin -- You received this message from the "vim_use" 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
