dougkearns at gmail.com
Mon Apr 17 08:00:35 EDT 2006
On Sun, Apr 16, 2006 at 11:52:07PM +0200, Nikolai Weibull wrote:
> On 4/16/06, Mark Guzman <segfault at hasno.info> wrote:
> > The commit also adds the work around for the cWORD problem Doug found.
> Actually, this isn't the right solution I think. The whole cWORD
> problem happens whenever a symbol is preceded by whitespace, not only
> when at the beginning of a line. One solution that works is calling
> VIM::command('normal! h') if the string is empty and then expanding.
> That way the cursor will be over the dot in ":x." and it will expand
> to the correct string. I really think that this should be fixed
> inside Vim instead, but Bram can't replicate our issue, so perhaps
> there something more to it than a simple bug in expand().
He can now and is fixing it. Apparently it requires 'encoding' to be set
More information about the vim-ruby-devel