Hi,
I found many typos in error messages and comments.
Attached patches fix them. I hope I didn't make another typo.
I used the spell checking feature in Vim to find these typos.
It was very useful but I think it's more useful if misspelled words
are listed using the quickfix window.
On 29-Apr-2013 13:10 +0200, Ken Takata wrote:
Hi,
[3 sentences deleted]
I used the spell checking feature in Vim to find these typos.
It was very useful but I think it's more useful if misspelled words
are listed using the quickfix window.
[...]
Thanks for taking care of these minor,
Taro Muraoka wrote:
Golang has very good plugins for vim. See this URL:
https://code.google.com/p/go/source/browse/#hg%2Fmisc%2Fvim
It would be great that if those are included in vim (7.4 maybe),
wouldn't it?
Please ask the author to send it to me. That makes it explicit that
these
ZyX wrote:
Isn't this breaking backwards compatibility? We would need to check
what Python plugins this breaks.
It is. I assume that nobody used `vim.buffers[i]` due to inability to
determine `i`. Case `for buffer in vim.buffers` which was likely used
to find buffer with given number
Comment #6 on issue 127 by fritzoph...@gmail.com: TFS Plugin Broken by
latest VIM
http://code.google.com/p/vim/issues/detail?id=127
Removing the ^ worked great, thank you. Was this a change to VIM's
behavior?
...sort of.
It's a change in the DEFAULT behavior.
Previously something like
The messages starting with E123: should be translated.
Internal messages, for developers only, do not need to be translated.
For others: Generally it's good to translate messages.
I am talking only about python exceptions. Except for possible Unicode*† errors
there is not much difference
Ken Takata wrote:
I found many typos in error messages and comments.
Attached patches fix them. I hope I didn't make another typo.
I used the spell checking feature in Vim to find these typos.
It was very useful but I think it's more useful if misspelled words
are listed using the
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 132 by charsb...@gmail.com: Crontab syntax highlighting doesn't
work properly when day/month names are not lowercased
http://code.google.com/p/vim/issues/detail?id=132
The crontab syntax file only highlights day and month
Comment #1 on issue 132 by vega.ja...@gmail.com: Crontab syntax
highlighting doesn't work properly when day/month names are not lowercased
http://code.google.com/p/vim/issues/detail?id=132
The syntax file used to ignore case (c.f., 0877b8d6370e) but was reverted
(accidentally?) when
Roland Eggner wrote:
Maybe your problem is caused by a discrepancy between locale configuration
and
installed fonts.
Suggestion (should work on Gentoo Linux, please tune to your macosx system):
(1) Uninstall locales, which you do not use, e.g.
su vim /etc/locale.gen
raf wrote:
Roland Eggner wrote:
Maybe your problem is caused by a discrepancy between locale configuration
and
installed fonts.
Suggestion (should work on Gentoo Linux, please tune to your macosx system):
(1) Uninstall locales, which you do not use, e.g.
su vim
raf wrote:
monolingual doesn't work on macosx-10.6.8. it requires 10.7+ so that's not an
option.
i guess i'll have to keep my little patch to disable E250 messages in place.
there's an older version that does work on macosx-10.6.8.
--
--
You received this message from the vim_dev
Hi! The following example contains a valid C99 (and C11) compound literal:
post(
letter,
(struct envelope){
.stamp = {
.value = ONE_CENT,
.pic = RAT
},
.address = address
}
);
Yet even after setting let c_no_curly_error = 1,
matchparen plugin in CursorMoveI autocmd is too slow while typing. So I
wish disable it in insert mode.
diff -r c61da758a9a2 runtime/doc/pi_paren.txt
--- a/runtime/doc/pi_paren.txt Wed Apr 24 18:34:45 2013 +0200
+++ b/runtime/doc/pi_paren.txt Tue Apr 30 12:45:56 2013 +0800
@@ -15,6 +15,10 @@
Hi. I also experienced this problem for some time.
I dicovered there was some editing mistakes in recent which
caused showing this message even if fontset is not used.
Patch which corrects the mistake is after the signature. It
soppressed the message for me.
The root cause is still unclear to
Hi. I also experienced this problem for some time.
I dicovered there was some editing mistakes in recent which
caused showing this message even if fontset is not used.
Patch which corrects the mistake is after the signature. It
soppressed the message for me.
The root cause is still unclear to
Hi,
Fixed the display of listchars characters on the cursorline visual-mode.
I've created a patch of two patterns.
I should not be judged because it is personal preference.
SpecialKey_overrides_CursorLine.patch
- Every highlighting listchars chatscters.
CursorLine_overrides_SpecialKey.patch
-
On 2013-04-30, Fanhe Fanhed wrote:
matchparen plugin in CursorMoveI autocmd is too slow while typing.
So I wish disable it in insert mode.
I don't understand. I don't even notice a delay when I type the
closing parenthesis and then more characters. Typing after the
closing parenthesis seems
18 matches
Mail list logo
