Re: [Cooker] Re: vim-5.6-4mdk
On Wed, Feb 09, 2000 at 05:31:57PM -0800, Brian J. Murrell wrote: from the quill of Chmouel Boudjnah [EMAIL PROTECTED] on scroll [EMAIL PROTECTED] Surely but i think it's hard to fix, why not using the vim-ctags ? Because the vim ctags is not available anywhere (Mandrake). I believe it is culled out of the vim package when the RPM is made. If the solution is to use the vim ctags then so be it, but if that's the case then the ctags package needs to deprecated in favour of having ctags bundled with vim. Unless you want to build the separate ctags package with the vim ctags that is. OK. I finally understand this thread!!! It's my fault, it's my own fault. Shame on me... I was wondering why people doesn't use the ctags bundled with the vim RPM. I guess this is because *I* didn't included ctags in the RPM. I'm going to fix this right now. This is not a problem localized to me. It is a bug in Linux Mandrake. Anyone using source with any uppercase identifiers in it will have this problem. This problem really is only one of sorting. Did vim change it's ctags format requirement from 5.5 to 5.6? Why would they do that? Did the ctags author change his sort since the last version? Why would he do that? I guess I am having trouble making sense out of this sudden incompatibility. It's a POSIX compatibility fix. The ctags bundled with vim is 3.4, which fixes some bugs. The standalone version of ctags is 3.2 and should be updated or deprecated. Chmouel, what do you think ? Should we remove Ctags-3.2 from cooker or should I make a standalone 3.4 version ? Sorry for this. DindinX -- [EMAIL PROTECTED]
Re: [Cooker] Re: vim-5.6-4mdk
"David Odin (aka DindinX)" [EMAIL PROTECTED] writes: or deprecated. Chmouel, what do you think ? Should we remove Ctags-3.2 from cooker or should I make a standalone 3.4 version ? Remove the ctags and provide a news ctags package from vim. -- MandrakeSoft http://www.mandrakesoft.com/ --Chmouel
Re: [Cooker] Re: vim-5.6-4mdk
from the quill of Chmouel Boudjnah [EMAIL PROTECTED] on scroll [EMAIL PROTECTED] Surely but i think it's hard to fix, why not using the vim-ctags ? Because the vim ctags is not available anywhere (Mandrake). I believe it is culled out of the vim package when the RPM is made. If the solution is to use the vim ctags then so be it, but if that's the case then the ctags package needs to deprecated in favour of having ctags bundled with vim. Unless you want to build the separate ctags package with the vim ctags that is. This is not a problem localized to me. It is a bug in Linux Mandrake. Anyone using source with any uppercase identifiers in it will have this problem. This problem really is only one of sorting. Did vim change it's ctags format requirement from 5.5 to 5.6? Why would they do that? Did the ctags author change his sort since the last version? Why would he do that? I guess I am having trouble making sense out of this sudden incompatibility. b. -- Brian J. Murrell InterLinx Support Services, Inc. North Vancouver, B.C. 604 983 UNIX Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
Re: [Cooker] Re: vim-5.6-4mdk
On Wed, 9 Feb 2000, Brian J. Murrell wrote: from the quill of Chmouel Boudjnah [EMAIL PROTECTED] on scroll [EMAIL PROTECTED] Surely but i think it's hard to fix, why not using the vim-ctags ? Because the vim ctags is not available anywhere (Mandrake). I believe it is culled out of the vim package when the RPM is made. If the solution is to use the vim ctags then so be it, but if that's the case then the ctags package needs to deprecated in favour of having ctags bundled with vim. Unless you want to build the separate ctags package with the vim ctags that is. This is not a problem localized to me. It is a bug in Linux Mandrake. Anyone using source with any uppercase identifiers in it will have this problem. This problem really is only one of sorting. Did vim change it's ctags format requirement from 5.5 to 5.6? Why would they do that? Did the ctags author change his sort since the last version? Why would he do that? I guess I am having trouble making sense out of this sudden incompatibility. b. Ok check it out there are two ways of sorting, Posix/ISO sorting, which seperates upper from lowwer case None ISO sorting, which does seperate them (god i hope i didn't mix those up, i'll be lynched) Anyways the only thing i see todo is make both available or it will just be an on going battle. and this iso non-iso crap they need to get their act together we have these same things elsewhere. :/ -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
