These are two new ebuilds, one to go on stable portage, while vimpart is for the kde-cvs modules which Dan maintains. The new kvim is in sync with main vim, and is in fact not compatible with it, since both provide the same executable. Actually, it is more up to date than main vim, as it includes patchsets up to 6.1.174 The vimpart ebuild provides embedded use of vim on konqueror, kdevelop, and all other apps which use kparts. I have thought about merging kvim's with vim's ebuild, but since they are not merged yet (kvim on mainline vim, that is), and kvim has a different version level, I think it is best to keep them separate for the time being. You might see that there is only one executable for vim, i.e., there are no separate executables with and without gui. That was because kde requires the file you feed to it is called vim and not kvim. Also, I think it is the standard behavior, to have the gui on the executable, and when you call it 'vim' it uses no gui, whereas if you call it 'kvim', 'gvim' or 'vim -g' it launches the gui. More details are included on the ebuild :) Please report back. I hope some of you are happy with this ebuild as I am using vim embedded in kde and with the nice kvim's gui interface which gives you both the power of vim's kerboard handling and the niceness and confortability of a well designed gui which fits with every other part of the system :)
hi, where are these ebuilds?
Created attachment 3788 [details] kvim ebuild and patches Gues, I'm really sorry for the delay. I tried and tried to send it from console browsers but I couldn't, I sent them by e-mail to two gentoo developers, but I guess they were even busier than I was. Well, I hope it goes well :)
Created attachment 3789 [details] vimpart ebuild, geared towards the kde-cvs branch You need the kde-cvs branch available on www.gentoo.org/~danarmak in irder to use this. I haven't added a kvim dependency since in theory it could work with other gui-enabled vim executables, although not all features would be available (namely MCOP).
i'm currently working on [kg ]vim ebuilds, please check http://gentoo.org/~hannes/app-editors/
hi, i just committed a new kvim ebuild, please try and check.
I have just tested the new kvim ebuild, and I have a few remarks about it. If you read the comments I posted earlier, you'll see I said that the executable had to be named just 'vim' for vimpart to work properly. My first rewrite of the kvim ebuild included the configure option '--with-vim-name=kvim' until I later realised that vimpart refused to use it as a gui-enabled vim. Also I'd like to see included the newer patches published by Braam Moolenaar. Finally, do you think it is really worth to have kvim completely merged with [g]vim? I say this because kvim is no yet integrated on vim's main branch, thus following a different, not-always synched path needing a different set of patches. They even use different sources. Finally, I am not that sure if it's better to have separate executables for different vims. In vim's philosophy, when you call the program by its simple name 'vim', you get access to console's version, whereas passing the option '-g' or using the symlink [g|k]vim, the gui is launched. The only thing one could miss with this approach is having access to different guis. I am not sure if you could compile vim with gtk and motif support at the same time. You can't do it with kde at this time, that's for sure, since kvim is not integrated yet... now that I think of it, the same happens with say Mozilla, you have access to different guis, but you have to decide at compile-time which one you want, don't you? Anyway, that's just my .02 cents :)) PS Please, do not think I did not like or appreciate your work, I like the way to tried to integrate things, really :)
fine, now we have a kvim-6.1.141.ebuild. you have any suggestions for this (patches which are not included?) the executable of kvim should be named vim in future (this will be done before vimpart goes into portage). vimpart depends on any graphical vim (or am I wrong?).
I'll check the committed ebuild and tell you what the differences with my own version are, if any. As far as the patches are concerned, they're the common patches - I'd say small updates/fixes better - available on ftp://ftp.vim.org/pub/vim/patches and which are updated on nearly a daily basis. Usually they're not that important - that is, urgent -, but since the old official ebuild included quite a few of them, I thought it'd be nice to keep in sync. I am not saying to commit a new ebuild every day, but to update them before commiting a new revision. If vimpart depends on a graphical vim? Sort of, it works with any graphical enabled build - I'm not sure which version it needs, but AFAIR, on the kdm frontend it says 'vim > 6.x' -, yet to take full advantage of all the available features, vimpart needs a DCOP enabled vim, what means kvim. And yes, the executable has to be named vim, otherwise vimpart's configurator will reject it for being a link, even if it is not. This might well be considered a bug to report to vimpart's maintainer, what do you think? Other than that, what I do have now on my own ebuild is a build of a fat kde enabled kvim executable, and a smaller 'vi' which only works from console, and does not need X nor qt or kde libs. That's what I think you intended when spliting the ebuilds into vim, kvim and gvim. I found that I sometimes need it, for example when upgrading qt/kde or even X, while you don't have the X/qt/kde libs on your path for vim to use, it is a pain in the ass not being able to launch your favorite editor. However there's the problem with vimpart requiring the executable to be named 'vim'. I know changing the name of the console-only as few dependencies as possible executable, to 'vi' is not a solution either, since there also exists a traditional old 'vi' package on gentoo. What's your opinion on that? P.S. Is there any way to interface with bugzilla from e-mail? I'd love to use mutt to manage all these comments and ebuild committing process on bugzilla.
well, it would be a feature request of vimpart to have anything like --with-vim-bin=/usr/bin/kvim in configure, we should report it to vimparts authors. i'm not really sure about vim and executables (i think the intention of the authors of vim is having one binary for all options called vim), the problem about this is if vim is compiled with kde-gui, there is vim and kvim is a symlink, when vim is executed as vim, the console vim is launched, if kvim is executed (or gvim for graphical vim or vim -g), the graphical vim is launched. the main problem is if you upgrade your X or kde, vim will not start (it is linked against a library which do not longer exists). my suggestion is to have multiple executables (vim for console vim, gvim for graphical vim, as it was before kvim got into portage, there was one vim ebuild which installed a console vim and gvim only if X, gnome or gtk was in use). so, having one vim ebuild would be nice (i will work on it), vimpart has then to depend on vim compiled with kde in use (see #2272). i will write the vimpart authors it would be nice to have such a configure option --with-vim-bin=/path/to/vim-binary a mail2bugzilla interface is afaik not available (if you find any, let me know).
Forgive me for not having replied on this entire week, but I had a death in the family and left the city where I am on back now for a few days. Your vim and vim-core ebuilds look just perfect. I am using them right now and the obtained 'vim' executable is slimmer than 'kvim' enough that there is no delay when loading it - there is a small delay with kvim, I guess as a consequence of the need to check for X and kde libraries, even if used on a console -. With respect to kvim ebuild, I'd just suggest to apply the same patches you apply on 'vim', since, after all it is the same program and it can benefit from the same patches; both the small gentoo-only ones, and the official ones available on vim's ftp. Other than that I am waiting, just as you are, for a modification to vimpart or its configurator to allow 'kvim' to be used. I still get: Test Failed! Your Vim does not provide any GUI support. A GUI is required to use this component. Upgrade your Vim's version or install GVim/KVim. Your Vim lacks the Eval feature; it is highly recommended to have this feature enabled. You may encounter problems without it. on vim component's configurator when I try to use kvim instead of vim.
Concerning my email2bugzilla question, after you used that name, I did a search on google, then read the official Bugzilla's FAQ and found the following: A.4.5. How do I set up the email interface to submit/change bugs via email? http://www.bugzilla.org/docs/html/faq.html#AEN1887 It seems it has to be setup on the server side. Do you know who maintains gentoo's bugzilla server? I also found there are some console tools to interface with bugzilla, there are some scripts in perl I found on the 'email2bugzilla' search, and there are also some included in bugzilla's contri directory, as stated in: C.2. Command-line Bugzilla Queries http://www.bugzilla.org/docs/html/cmdline.html P.S. Sorry for being off-topic, I guess this is not the right place to talk about this.
sorry for not responding for a long time. current status is unknown ;) have no answer if kvim supports --with-bin=kvim/ kde will support a vim named kvim. i also have problems with vim patches, they do not apply well. kvim should also use vim.eclass... it's a lot of work to do, and i've currently not much time for kvim, if you want to make an ebuild which uses vim.eclass (i think you've first to patch vim.eclass), please do.
I'll close this bug for now, as the last comment was allready a long time ago.
see paul's comment above
