[EMAIL PROTECTED] wrote: > Thanks, Tony! That was a fast reply. > >>> Making GUI_INC_LOC call configure sounds wicked to me. > The effect of the "env" command is like export. I did that when > pursuing someone else's tip at some point, and apparently didn't even > think about the syntax being unnecessarily different. No worries > though. (Although I am offering you assurances, I switched it to a > separate envariable "export" and I'm re-running my little build > script. Just to make sure.)
see my "oops" reply > >>> Try making your calls more standard. You may want to use my howto page >>> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm as a source of >>> inspiration. > Thanks, I have started digesting some of what you've written there. > It has led me to the 7.1 patches, which I had not known about before. > Cool. If you compile Vim yourself, you should stay subscribed to vim_dev. Bram publishes all patches there in email form, usually at about the same time that they arrive at the FTP server. However, personally I prefer the FTP server because my ISP's mail servers sometimes (and unpredictably) convert mail any which way between 8bit, quoted-printable and (aargh!) base64. Also, if several patches arrive within a short time interval, I can use multiple-get over FTP, and get the updated README (table of contents) with them. The latest patch I had to use from email, but (luckily) the Google mail servers delivered it to me in "8bit" Content-Transfer-Encoding, so I could use it "as is". > > Looks like many more pointers to read there. Thanks, > > --Chris-- My pleasure. Best regards, Tony. -- Ankh if you love Isis. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
