Summary: | new emerge of VIM - displays strange characters while editing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kirk <khoganson> |
Component: | Current packages | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kirk
2005-07-05 09:50:47 UTC
The problem oddly enough was my USE flag setting. It was specifically the -* i used to deselect everything I hadn't specifically asked for. I am not sure why this caused the problem, as I haven't gone through and duplicated the flag changes that created. However, removing it and recompiling vim and all dependencies has cleared up this little issue. Is this removing some kind of hidden flag for vim, or was it one of the listed options that is now being included? it may have been removing NLS support. It does depend on locale and terminal. Isn't this still a bug? Perhaps I'm missing something here, but VIM is used a great deal, and the -* flag has been suggested quite often on the forums recently as a way to avoid installing new dependencies you didn't have USE flags set for. The two together are broken. Shouldn't VIM handle this flag more gracefully? The -* is bad advice. Some of the USE flags are defaulted on purpose on some platforms, and disabled on others. Try including the ncurses or termcap-compat USE flag, and maybe it will fix your problem. The -* seemed a little sketchy to me as well. That is why I eliminated it from my flags when I did for testing. I am not still having trouble as I removed it, and won't be adding it again. I am just putting forth the general idea of handling the -*. Though in retrospect I think that the better way of handling this is to discourage use of -*, as other packages probably do not handle this well either. |