Thread: [A-a-p-user] vim update
Brought to you by:
vimboss
From: Andreas C. <And...@bo...> - 2006-05-09 09:09:48
|
I am trying to update Vim to 7.0 via aap update. The following error = occurs:=20 if_python.c: In function `BufferNew': if_python.c:1312: error: structure has no member named `python_ref' Other errors of the same kind follow for other functions.=20 My OS is suse9.3, python is 2.4, aap is 1.088. config.arg: --enable-cscope --enable-pythoninterp --with-python-config-dir=3D/usr/lib/python/config I would be lucky for help. |
From: Andreas C. <And...@bo...> - 2006-05-09 09:18:51
|
I am trying to update Vim to 7.0 via aap update. The following error = occurs:=20 if_python.c: In function `BufferNew': if_python.c:1312: error: structure has no member named `python_ref' Other errors of the same kind follow for other functions.=20 My OS is suse9.3, python is 2.4, aap is 1.088. config.arg: --enable-cscope --enable-pythoninterp --with-python-config-dir=3D/usr/lib/python/config I would be grateful for help. Regards, Andreas Clausen |
From: Bram M. <Br...@mo...> - 2006-05-09 10:31:31
|
Andreas Clausen wrote: > I am trying to update Vim to 7.0 via aap update. The following error occurs: > > if_python.c: In function `BufferNew': > if_python.c:1312: error: structure has no member named `python_ref' > > Other errors of the same kind follow for other functions. > My OS is suse9.3, python is 2.4, aap is 1.088. > > config.arg: > --enable-cscope > --enable-pythoninterp > --with-python-config-dir=/usr/lib/python/config > > I would be grateful for help. It looks like you still have an old version if_python.c, "pyton_ref" was renamed to "b_python_ref". CVS is lagging behind, the SourceForge server is broken. You might have more success with "aap update CVS=no". -- hundred-and-one symptoms of being an internet addict: 61. Your best friends know your e-mail address, but neither your phone number nor the address where you live. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |
From: calmar <ma...@ca...> - 2007-02-12 13:17:28
|
On Tue, May 09, 2006 at 11:09:44AM +0200, Andreas Clausen wrote: Hi all, > config.arg: > --enable-cscope > --enable-pythoninterp > --with-python-config-dir=/usr/lib/python/config Maybe I'm dumber than others, but to me, it wasn't clear what to do here: http://www.a-a-p.org/ports.html about that config.arg I actually did the same like above, but it was more a guess. I won't know if the arguments must be on its own line. Additionally there was no such file around, what was confusing. How about putting there an example file (in the case there are comments allowed: ,--------src/config.arg ------------- | ######################### | # put your configure options below like e.g.: | #--enable-OPTION1 | #--enable-OPTION2 | #....... | | | | `--- then when someone reads it, on a-a-p, he looks for that file, he finds it, opens ist, and just sees what is to do. But then, I'm still not really sure, that's the way to do it, but the things I wanted compiled in are there, so. Addititionally it wasn't clear how to do that 'aap fetch'. So calling aap without anything, actually configures and compiles it. ok. probably the proper thing would be for people who wants to add configure-options: aap -f http://www.a-a-p.org/vim/main.aap fetch {CVS=no} ? Anyway, cheers and thanks, marco -- (o_ It rocks: LINUX + Command-Line-Interface //\ V_/_ http://www.calmar.ws |
From: Bram M. <Br...@mo...> - 2007-02-13 02:08:46
|
Marco wrote: > On Tue, May 09, 2006 at 11:09:44AM +0200, Andreas Clausen wrote: > > Hi all, > > > config.arg: > > --enable-cscope > > --enable-pythoninterp > > --with-python-config-dir=/usr/lib/python/config > > Maybe I'm dumber than others, but to me, it wasn't clear what to > do here: http://www.a-a-p.org/ports.html about that config.arg > > I actually did the same like above, but it was more a guess. > I won't know if the arguments must be on its own line. > > Additionally there was no such file around, what was confusing. > > How about putting there an example file (in the case there are > comments allowed: It is left out intentional: you are expected to change this file. If it would be included in the distribution you would get conflicts when updating to a newer version. Could add a config.arg.example file perhaps. > ,--------src/config.arg ------------- > | ######################### > | # put your configure options below like e.g.: > | #--enable-OPTION1 > | #--enable-OPTION2 > | #....... This would quickly become a duplicate of what is in Makefile. > then when someone reads it, on a-a-p, he looks for that file, he > finds it, opens ist, and just sees what is to do. > > But then, I'm still not really sure, that's the way to do it, but > the things I wanted compiled in are there, so. > > > Addititionally it wasn't clear how to do that 'aap fetch'. So > calling aap without anything, actually configures and compiles it. > ok. That works too. "aap fetch" only gets the files. > probably the proper thing would be for people who wants to add > configure-options: > > aap -f http://www.a-a-p.org/vim/main.aap fetch {CVS=no} Yes, so that in between fetching and building you can edit that config.arg file. The idea was that this would become the default way to remember compilation options. Currently everybody has their own way of doing it. -- In a world without walls and borders, who needs windows and gates? /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |
From: calmar <ma...@ca...> - 2007-02-13 07:02:09
|
On Tue, Feb 13, 2007 at 03:11:33AM +0100, Bram Moolenaar wrote: Hi Bram, > > > > How about putting there an example file (in the case there are > > comments allowed: > > It is left out intentional: you are expected to change this file. If it > would be included in the distribution you would get conflicts when > updating to a newer version. > > Could add a config.arg.example file perhaps. > > > ,--------src/config.arg ------------- > > | ######################### > > | # put your configure options below like e.g.: [...] > > This would quickly become a duplicate of what is in Makefile. Maybe tweaking the http://www.a-a-p.org/ports.html somebit with some additionaly notes like here: http://www.calmar.ws/tmp/aap.html (there is this example linked: http://www.calmar.ws/tmp/config.arg.html I won't know if comments are acceptable there so) To me personally at least, that would clear up things somebit, so there is no need for guessing (and thinking) anymore ;) cheers and thanks, marco PS: (the thing above and especially the things below are a little bit a 'webmaster' issue, probably I should send that to them?) I won't really know, but http://vim.org does not work (without the www). in .htaccess: RewriteCond %{HTTP_HOST} ^vim.org RewriteRule (.*) http://www.vim.org/$1 [R=301,L] would redirect users who only enter 'vim.org' and expect to accessa but fail - dunno how many try to do so, so. I did several times already, and don't understand really why it's 'disabled' really. The same thing (.htaccess on apache) would also work on http://a-a-p.org . Meta-directs (what is there actually) can be evil, I had to learn the hard way recently. -- (o_ It rocks: LINUX + Command-Line-Interface //\ V_/_ http://www.calmar.ws |
From: Bram M. <Br...@mo...> - 2007-02-15 02:28:34
|
Calmar wrote: > > > How about putting there an example file (in the case there are > > > comments allowed: > > > > It is left out intentional: you are expected to change this file. If it > > would be included in the distribution you would get conflicts when > > updating to a newer version. > > > > Could add a config.arg.example file perhaps. > > > > > ,--------src/config.arg ------------- > > > | ######################### > > > | # put your configure options below like e.g.: > [...] > > > > This would quickly become a duplicate of what is in Makefile. > > Maybe tweaking the http://www.a-a-p.org/ports.html somebit with > some additionaly notes like here: > > http://www.calmar.ws/tmp/aap.html > > (there is this example linked: http://www.calmar.ws/tmp/config.arg.html > I won't know if comments are acceptable there so) Thanks for the tip and example. > To me personally at least, that would clear up things somebit, so > there is no need for guessing (and thinking) anymore ;) That's right. > PS: (the thing above and especially the things below are a little > bit a 'webmaster' issue, probably I should send that to them?) > > I won't really know, but http://vim.org does not work (without > the www). Known issue, it's mainly to make CVS access work. > in .htaccess: > > RewriteCond %{HTTP_HOST} ^vim.org > RewriteRule (.*) http://www.vim.org/$1 [R=301,L] > > would redirect users who only enter 'vim.org' and expect to > accessa but fail - dunno how many try to do so, so. I did several > times already, and don't understand really why it's 'disabled' > really. I don't think the rewrite helps, it's a DNS thing. It actually works in firefox, I think firefox adds the "www." when it doesn't work without. > The same thing (.htaccess on apache) would also work on > http://a-a-p.org . Meta-directs (what is there actually) can be > evil, I had to learn the hard way recently. What is so bad about meta stuff? -- "A clear conscience is usually the sign of a bad memory." -- Steven Wright /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |
From: calmar <ma...@ca...> - 2007-02-15 07:47:14
|
On Thu, Feb 15, 2007 at 03:31:20AM +0100, Bram Moolenaar wrote: Hi Bram, > > The same thing (.htaccess on apache) would also work on > > http://a-a-p.org . Meta-directs (what is there actually) can be > > evil, I had to learn the hard way recently. > > What is so bad about meta stuff? e.g. http://www.webweaver.nu/html-tips/web-redirection.shtml (see Method 2) Anyway, in the http://a-a-p.org case, there probably won't result bad things out of it, it's still not the way how it should get done I think. My personal notes about it below (may ignore so): Search-Engines actually ignore them, or even see something bad at them: 'ah. someone wants to show me (robot) this, but the user shall see something different'. Search engines will still index/cache that thing there, it would not when there is some permanent redirect. http://groups.google.com/group/Google_Webmaster_Help there are also quite some articles about it. I personally had somekind of 'hell' recently, because I was using those redirects, assuming the robots would understand them and behave accordingly. They didn't. That whole thing ended up that google had the same pages on the old and new domain, and therefore sent the new one to the end of the search-results (500+) because of the 'same content filter' or so. Actually after 3 month now, it's ok (puhhh) - it removed those old pages from the cache finally. Additionally permanent redirects, be it .htaccess or php, transfer the 'value' of the old pages to the new ones, just in case. That workes quite nice, had to do that recently ;) (Also not a matter in a-a-p.org so). Cheers marco > > -- > "A clear conscience is usually the sign of a bad memory." > -- Steven Wright > > /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ download, build and distribute -- http://www.A-A-P.org /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- (o_ It rocks: LINUX + Command-Line-Interface //\ V_/_ http://www.calmar.ws |
From: Bram M. <Br...@mo...> - 2007-02-16 05:08:04
|
Marco wrote: > On Thu, Feb 15, 2007 at 03:31:20AM +0100, Bram Moolenaar wrote: > > Hi Bram, > > > The same thing (.htaccess on apache) would also work on > > > http://a-a-p.org . Meta-directs (what is there actually) can be > > > evil, I had to learn the hard way recently. > > > > What is so bad about meta stuff? > > e.g. > http://www.webweaver.nu/html-tips/web-redirection.shtml > > (see Method 2) > > Anyway, in the http://a-a-p.org case, there probably won't result > bad things out of it, it's still not the way how it should get > done I think. > > > My personal notes about it below (may ignore so): > > Search-Engines actually ignore them, or even see something bad at > them: 'ah. someone wants to show me (robot) this, but the user > shall see something different'. > > Search engines will still index/cache that thing there, it would > not when there is some permanent redirect. > > http://groups.google.com/group/Google_Webmaster_Help there are > also quite some articles about it. > > I personally had somekind of 'hell' recently, because I was using > those redirects, assuming the robots would understand them and > behave accordingly. They didn't. That whole thing ended up that > google had the same pages on the old and new domain, and therefore > sent the new one to the end of the search-results (500+) because > of the 'same content filter' or so. Actually after 3 month now, > it's ok (puhhh) - it removed those old pages from the cache > finally. > > Additionally permanent redirects, be it .htaccess or php, transfer > the 'value' of the old pages to the new ones, just in case. That > workes quite nice, had to do that recently ;) (Also not a matter > in a-a-p.org so). Thanks for the hints. SourceForge is currently down, I'll look into this later. -- hundred-and-one symptoms of being an internet addict: 130. You can't get out of your desk even if it's time to eat or time to go to the bathroom. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// |