Now there's finally a patch for vim, that enables it to handle split windows - where one of them is a shell. This should definetely be a USE variable. Reproducible: Always Steps to Reproduce: 1. 2. 3.
not a bugzilla bug
No - never said it was - I marked it as a feature request - and it's for the vim ebuild.
What is wrong with using the vimsh script? http://vim.sourceforge.net/scripts/script.php?script_id=165
Well - in the readme the author himself says there are things that aren't optimal - so I'd like to be able to test both ways of doing it - freedom of choice you know ;) and I didn't know about vimsh script - trying it out now.
vimsh really isn't that good compared to the shell. Although, the shell doesn't work in gvim, only vim so far. On the other hand, this is another one of those big probably high maintenance patches that'll likely be included with vim7, so I'm kinda leaning towards a WONTFIX, at least for vim6. Ryan?
Arggh - found one BIG reason for using the patch instead. vimsh.vim does NOT support tab-completion :( (me feels like being back on old windows)
If you "know" it'll be included in vim7 - and we can have a vim7 cvs ebuild (with it included) I'll be content ;) otherwise, I'd rather have a USE option for vim6 - that works for the versions the author wrote it for - as to not be too high maintenance for you guys. Does portage support ~x86 for USE options only? ;)
I don't know for sure that it'll be in vim7, but if the patch is made to really work reliably then chances are it'll make it in at some point in the future. As for vim6, personally I'm not a fan of adding in our own large complicated patches since they tend to cause serious problems when upstream stop maintaining them... It's why we don't apply the conceal patch either.
Well it would be nice to have in unstable - does portage not support ~x86 USE options, even if the ebuild is stable? Def. a nice2have feature IMHO :)
I don't think the patch is stable enough, nor does it add a high priority, must fix feature, to vim. Another thing going against it is the inability to work with gvim. The two apps coincide closely together and I like vim and gvim having the same functionalty; i'm sure other people also. I think a WONTFIX would be warranted.
Ok, going with WONTFIX. I might stick it in the masked vim7 ebuilds at some point just to see how well it works, but not in vim6.
*** Bug 104595 has been marked as a duplicate of this bug. ***
*** Bug 157469 has been marked as a duplicate of this bug. ***
*** Bug 164303 has been marked as a duplicate of this bug. ***
