Hi Kartik,
2012/11/01 Thu 17:20:14 UTC+9 Kartik Agaram:
> Thanks, Tony. It seems to be because of a call to mb_string2cells in
>
> if_py_both.h:VimStrWidth. Since python isn't a feature in feature.h
>
> I'm not sure what to check for to enable FEAT_MBYTE..
I don't think +python should depends +multi_byte because there are
patches which fix similar problem (7.3.232 and 7.236).
This problem seems to be caused by 7.3.569.
Please try the attached patch.
Best regards,
Ken Takata
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
# HG changeset patch
# Parent 9b28663dc44b4006d95dea330bc55f23c19eb2fe
diff --git a/src/if_py_both.h b/src/if_py_both.h
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -520,7 +520,13 @@
if (!PyArg_ParseTuple(args, "s", &expr))
return NULL;
- return PyLong_FromLong(mb_string2cells((char_u *)expr, (int)STRLEN(expr)));
+ return PyLong_FromLong(
+#ifdef FEAT_MBYTE
+ mb_string2cells((char_u *)expr, (int)STRLEN(expr))
+#else
+ STRLEN(expr)
+#endif
+ );
}
/*
