[patch] fix fi.po to pass test51

2013-04-19 Fir de Conversatie Niko Mikkilä
Hi, test51 fails when using Finnish translations because of a missing colon character in the E475 message string. This causes Vim builds to fail on Debian and Ubuntu when the user already has Vim localizations installed to the system and uses a Finnish locale. Attached patch for fi.po fixes

Re: gVim's internal borders

2013-04-19 Fir de Conversatie Ben Fritz
On Thursday, April 18, 2013 10:40:48 PM UTC-5, vee...@veegee.org wrote: On Thursday, April 18, 2013 10:18:22 PM UTC-4, aschneiderg wrote: Hey there. Are your builds available online ? I would like to check them out. All the best. Uploaded for you guys. Couldn't find any 64-bit

Re: Issue 104 in vim: Incorrect commentstring option for lisp

2013-04-19 Fir de Conversatie vim
Comment #3 on issue 104 by j...@bendyworks.com: Incorrect commentstring option for lisp http://code.google.com/p/vim/issues/detail?id=104 This has been fixed as of vim 7.3.875, so this issue can be closed. Thanks! -- You received this message because this project is configured to send all

Re: Variable for motion type in Operator-pending mode

2013-04-19 Fir de Conversatie Ingo Karkat
On 18-Apr-2013 16:16 +0200, glts wrote: Hi, I have recently learnt of a patch that was submitted to the list almost five years ago. Please see here: https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ Oh dear, I remember that! It's frightening how quickly time passes :-)

[bug] hanging vim

2013-04-19 Fir de Conversatie Christian Brabandt
Hi, every once in a while, Vim seems to hang and becomes unresponsive. Now I finally got a bt. In the current stack trace, the rails.vim plugin seems to cause this, but this has also happened, when using vim -u NONE -N Only passing -X seems to prevent this. For some reason, this seems to always

Re: Variable for motion type in Operator-pending mode

2013-04-19 Fir de Conversatie glts
Ingo, On Fri, Apr 19, 2013 at 8:58 PM, Ingo Karkat sw...@ingo-karkat.de wrote: On 18-Apr-2013 16:16 +0200, glts wrote: As for the name of the variable, how about: v:motiontype The documentation says that when no motion type is given the variable will be empty, when an explicit motion

[bug] searching for []

2013-04-19 Fir de Conversatie Christian Brabandt
Bram, I noticed, that searching in Vim for [] will match '[]' literally. This seems to be a little bit unexpected, because I would either expect to match everything because the collation [] contains nothing, or an error message, since we are missing a closing ']' as grep or awk does (also nvi):

Re: [bug] searching for []

2013-04-19 Fir de Conversatie Tony Mechelynck
On 19/04/13 23:57, Christian Brabandt wrote: Bram, I noticed, that searching in Vim for [] will match '[]' literally. This seems to be a little bit unexpected, because I would either expect to match everything because the collation [] contains nothing, or an error message, since we are missing

Re: Variable for motion type in Operator-pending mode

2013-04-19 Fir de Conversatie Kana Natsuno
On Saturday, April 20, 2013 6:50:58 AM UTC+9, glts wrote: On Fri, Apr 19, 2013 at 8:58 PM, Ingo Karkat wrote: With v:motiontype, I'd expect that to be applicable to _every_ motion, not just those few special ones. I would prefer v:forcedmotiontype. The only saving grace for this unreadable