gvim complains if the executable (vim) has the setuid bit on. I found out the hard way. I thought maybe making it setuid to root would work, albeit making all new files belong to root! Since we're talking about a temporary file made within vim/gvim itself, the file comes and goes. There's no way to check its permissions. I've toyed with trying to make a debug version of vim so that I can find out what's going on.
I'm not doing anything strange here at all. Just make install (as root, which is correct), and then using gvim. Certainly there must be other Linux users trying to use version 7.2 that are running into the same problem! Warren D. Swan - “Woods” IT Architect, SCM SME IBM Global Point of Sale Team; Wal-Mart Enterprise [email protected] Office: 479-277-5065 Cell: 417-846-6385 From: "Gene Kwiecinski" <[email protected]> To: <[email protected]> Date: 04/28/2009 05:25 PM Subject: RE: VIm 7.2 on Linux - bug in temporary files Check the permissions of the file itself. Might have some setuid bit set in the executable, permissions on the file disallowing you from reading it (eg, 0600), or other sneakery going on. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
