Re: A suggestion about runtime files and documentation

2007-01-31 Thread DervishD
Hi Bram :) * Bram Moolenaar [EMAIL PROTECTED] dixit: DervishD wrote: I mean, that's not the point. The point is that the source code is using hardcoded directories, and that is not a good practice, even if you force to have all runtime files under the same directory, because

Re: A suggestion about runtime files and documentation

2007-01-31 Thread DervishD
Hi Tony :) * A.J.Mechelynck [EMAIL PROTECTED] dixit: Bram Moolenaar wrote: [...] I don't see how getting rid of hardcoded directories in the source code is going to cause problems for users ;) In fact, hardcoded directories may cause problems: if you modify src/Makefile and don't

Re: A suggestion about runtime files and documentation

2007-01-30 Thread DervishD
Hi Bram :) * Bram Moolenaar [EMAIL PROTECTED] dixit: DervishD wrote: Don't take me wrong: I'm not critisizing Bram's amazing work with Vim, and I'm not asking for this to be fixed. What I really mean is that Vim will be more flexible if it doesn't have that hardcoded paths and

Re: A suggestion about runtime files and documentation

2007-01-30 Thread Bram Moolenaar
DervishD wrote: I mean, that's not the point. The point is that the source code is using hardcoded directories, and that is not a good practice, even if you force to have all runtime files under the same directory, because someone could change one of the many variables under src/Makefile

Re: A suggestion about runtime files and documentation

2007-01-29 Thread Bram Moolenaar
DervishD wrote: Hi all, specially Bram :) The source code for vim is full of hardcoded directories, rendering useless the constants defined in src/Makefile. Moreover, it doesn't use configure values to establish locations, but that's a minor problem. The major problem is that this