Bug#684929: display glitches when used with centerim

2012-10-13 Thread Tim Pope
Package: screen Version: 4.1.0~20120320gitdb59704-7 Severity: normal I dug a bit deeper and discovered that the problem is that the Linux console is being erroneously detected as an xterm. You can confirm this by running :dinfo and noting xterm in the output. I traced it back to this code from

Bug#462418: ruby.vim-ftplugin_ri.diff is obsolete

2008-01-24 Thread Tim Pope
Package: vim Version: 1:7.1-175+2 Severity: minor The patch ruby.vim-ftplugin_ri.diff sets keywordprg=ri for Ruby files. As of 7.1, the runtime file does this anyways, in a manner that more intelligently takes into account the limitations of running programs in GVim. The patch should be removed.

Bug#389332: iskeyword in ftplugin/ruby.vim causes problems

2007-02-28 Thread Tim Pope
ing at its default and changing it causes code like !File.exists?(".vimrc") to highlight incorrectly. Because of the way ri searches, omitting the ? or ! from the method name (as would happen if the iskeyword line is removed) will not typically impact the results. Thanks, Tim Pope -- To U

Bug#347790: xterm: boldMode patch

2006-03-19 Thread Tim Pope
Here's a second attempt. Perhaps you can tell me if I'm on the right track. Is this how you would go about it? Thanks, Tim Pope --- fontutils.c 2006-03-14 15:14:11.0 -0600 +++ fontutils.c.dealloc-later 2006-03-19 14:29:02.0 -0600 @@ -789,6 +789,12 @@ bfs = nfs;

Bug#347790: xterm: boldMode patch

2006-03-14 Thread Tim Pope
. This, in my opinion, is more useful, more consistent, and better coincides with the description in the manpage. Cheers, Tim Pope -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (700, 'stable'), (500, 'tes