Re: Issue 102 in vim: Cursor at incorrect location after doing substitution %s/x/y/c when file contains folds

2013-01-12 Fir de Conversatie vim
Comment #1 on issue 102 by dominiqu...@gmail.com: Cursor at incorrect location after doing substitution %s/x/y/c when file contains folds http://code.google.com/p/vim/issues/detail?id=102 Christian Brabandt wrote: Here is a patch: diff --git a/src/ex_cmds.c b/src/ex_cmds.c ---

[PATCH] Add :function defaults: resets some options that are likely to cause problems when function is run

2013-01-12 Fir de Conversatie ZyX
Note about #ifdef FEAT_EVAL in src/option.c: this is for making it possible to use :map defaults in the future (when I find a way to do so): resetting options to default values when mapping is run. # HG changeset patch # User ZyX kp-...@ya.ru # Date 1357992946 -14400 # Node ID

:view does not always set 'readonly'

2013-01-12 Fir de Conversatie Andy Wokula
:view does not always set 'readonly': :e somefile.txt :split :view or :e somefile.txt :sview Looks like a bug. -- Andy -- 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,

Re: scala syntax file.

2013-01-12 Fir de Conversatie Bram Moolenaar
Catalin Ciurea wrote: Is this Scala syntax file going to be integrated in Vim tree ? https://github.com/scala/scala-dist/tree/master/tool-support/src/vim It was made by contributors to the Scala project. For a file to be included in the distribution it has to be emailed to me.

Re: :view does not always set 'readonly'

2013-01-12 Fir de Conversatie Christian Brabandt
Hi Andy! On Sa, 12 Jan 2013, Andy Wokula wrote: :view does not always set 'readonly': :e somefile.txt :split :view or :e somefile.txt :sview Looks like a bug. That is on purpose. I don't know why ,[ vim ex_docmd.c ]- | else if (readonlymode

[PATCH] Make pyeval() print stack traces (unless :silence’d)

2013-01-12 Fir de Conversatie ZyX
# HG changeset patch # User ZyX kp-...@ya.ru # Date 1358006430 -14400 # Node ID 9c4ad944627dc19bd898174c8fe28a5ee0de4c26 # Parent b89e2bdcc6e516d7e8cbcb3ece9961ffe18b45fa Made pyeval()/py3eval() also print error messages diff -r b89e2bdcc6e5 -r 9c4ad944627d src/if_python.c --- a/src/if_python.c

Re: [PATCH] Add :function defaults: resets some options that are likely to cause problems when function is run

2013-01-12 Fir de Conversatie Bram Moolenaar
ZyX wrote: Note about #ifdef FEAT_EVAL in src/option.c: this is for making it possible to use :map defaults in the future (when I find a way to do so): resetting options to default values when mapping is run. # HG changeset patch # User ZyX kp-...@ya.ru # Date 1357992946 -14400 # Node

Re: [PATCH] Add :function defaults: resets some options that are likely to cause problems when function is run

2013-01-12 Fir de Conversatie ZyX
суббота, 12 января 2013 г., 20:29:58 UTC+4 пользователь Bram Moolenaar написал: I like the idea. But doing this specifically for functions may not be the best solution. Why? autocommands, mappings and commands almost always call functions that do the action for almost any plugin that is more