Re: allow to vimgrep current buffer

2014-10-31 Fir de Conversatie Bram Moolenaar
Zyx wrote: On October 29, 2014 10:54:38 PM EAT, Bram Moolenaar b...@moolenaar.net wrote: Christian wrote: On Di, 28 Okt 2014, Ingo Karkat wrote: Well, then perhaps a separate :bvimgrep[add] set of commands would be better than overloading the existing commands:

Patch 7.4.489

2014-10-31 Fir de Conversatie Bram Moolenaar
Patch 7.4.489 Problem:Cursor movement still wrong when 'lbr' is set and there is a number column. (Hirohito Higashi) Solution: Add correction for number column. (Hiroyuki Takagi) Files: src/charset.c *** ../vim-7.4.488/src/charset.c2014-10-15 21:26:35.566082778

Re: Patch 7.4.473

2014-10-31 Fir de Conversatie Bram Moolenaar
Hirohito Higashi wrote: Hi Bram and Christian, 2014/10/10(Fri) 22:34:57 UTC+9 Bram Moolenaar: Patch 7.4.473 Problem:Cursor movement is incorrect when there is a number column/sign/fold column and 'sbr' is displayed. Solution: Adjust the column for 'sbr'. (Christian

Re: [patch] Put ~ markers into their own highlight group

2014-10-31 Fir de Conversatie Bram Moolenaar
Marco Hinz wrote: this might be yet another controversial patch, but it's asked for on IRC all the time. The problem is that the ~ markers (end of buffer) and parts of 'listchars' both use the same highlight group: NonText. Now people wish to use different colors for this, thus this

Re: [patch] Use a [count] for do/dp as the [bufspec] for :diffget/:diffput

2014-10-31 Fir de Conversatie Bram Moolenaar
James McCoy wrote: Needing to fallback to :diffget/:diffput instead of do/dp when dealing with a 3-way diff has always bothered me. I've been having to do that more lately, so the attached patch turns a supplied [count] for do/dp into the [bufspec] for :diffget/:diffput. Obviously, it's

Patch 7.4.490

2014-10-31 Fir de Conversatie Bram Moolenaar
Patch 7.4.490 Problem:Cannot specify the buffer to use for do and dp, making them useless for three-way diff. Solution: Use the count as the buffer number. (James McCoy) Files: runtime/doc/diff.txt, src/diff.c, src/normal.c, src/proto/diff.pro ***

Re: [patch] When specify a negative number to 'topline' by winrestview(), display becomes strange.

2014-10-31 Fir de Conversatie Bram Moolenaar
Hirohito Higashi wrote: Hi list! How to reproduce: - start vim $ vim -N -u NONE -c se nu - Input below. iaEsc :call winrestview({'topline': -3}) Expected behavior: - Display this. (Display does not change) 1 a Actual behavior: - Displayed below. (Invalid line

Patch 7.4.491

2014-10-31 Fir de Conversatie Bram Moolenaar
Patch 7.4.491 Problem:When winrestview() has a negative topline value there are display errors. Solution: Correct a negative value to 1. (Hirohito Higashi) Files: src/eval.c *** ../vim-7.4.490/src/eval.c 2014-09-19 20:45:19.266454650 +0200 --- src/eval.c 2014-10-31

append mode for writefile()

2014-10-31 Fir de Conversatie mattn
a mode is usefull to append text/binary into the file. For example, writing log file. redir isn't work with nesting call. And verbosefile contains needless contents. I know :wfile but it need buffer contains text to append. So currently, vim doesn't have a seamless way to append text into a

Re: append mode for writefile()

2014-10-31 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: a mode is usefull to append text/binary into the file. For example, writing log file. redir isn't work with nesting call. And verbosefile contains needless contents. I know :wfile but it need buffer contains text to append. So currently, vim doesn't have a seamless

Re: [patch] switch nfa regexp engine to bt engine when too many states are encountered

2014-10-31 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: On Fr, 10 Okt 2014, Christian Brabandt wrote: Hi Bram! On Do, 09 Okt 2014, Bram Moolenaar wrote: Christian wrote: Bram, here is patch, that will switch from the NFA engine to the BT regular expression engine when there are

Patch 7.4.492

2014-10-31 Fir de Conversatie Bram Moolenaar
Patch 7.4.492 Problem:In Insert mode, after inserting a newline that inserts a comment leader, CTRL-O moves to the right. (ZyX) Issue 57. Solution: Correct the condition for moving the cursor back to the NUL. (Christian Brabandt) Files: src/edit.c,

Re: Issue 57 in vim: After creating a new line using CR C-o moves one character forward

2014-10-31 Fir de Conversatie vim
Updates: Status: Fixed Comment #2 on issue 57 by brammool...@gmail.com: After creating a new line using CR C-o moves one character forward https://code.google.com/p/vim/issues/detail?id=57 Fixed by patch 7.4.492 -- You received this message because this project is configured to send

Patch 7.4.493

2014-10-31 Fir de Conversatie Bram Moolenaar
Patch 7.4.493 Problem:A TextChanged autocommand is triggered when saving a file. (William Gardner) Solution: Update last_changedtick after calling unchanged(). (Christian Brabandt) Files: src/fileio.c *** ../vim-7.4.492/src/fileio.c 2014-09-23

Re: Issue 267 in vim: Segmentation fault with if_lua (during or after the GC)

2014-10-31 Fir de Conversatie vim
Comment #1 on issue 267 by plus...@gmail.com: Segmentation fault with if_lua (during or after the GC) https://code.google.com/p/vim/issues/detail?id=267 Same here, use neocomplete with if_lua, vim simply crash if I don't use it for a while. -- You received this message because this

support XDG_CONFIG_HOME environment variable for gitconfig filetype

2014-10-31 Fir de Conversatie Jerome Reybert
Hi, this is my first patch to vim, I hope I do it right I recently started to use the xdg environment, more specifically the environement variable XDG_CONFIG_HOME, to move some of my configuration files, such as .gitconfig. I set XDG_CONFIG_HOME to something else than ~/.config . There are

support XDG_CONFIG_HOME environment variable for gitconfig filetype

2014-10-31 Fir de Conversatie Jerome Reybert
Hi, this is my first patch to vim, I hope I do it right ;) I recently started to use the xdg environment, more specifically the environement variable XDG_CONFIG_HOME, to move some of my configuration files, such as .gitconfig. I set XDG_CONFIG_HOME to something else than ~/.config . There

Re: Put ~ markers into their own highlight group

2014-10-31 Fir de Conversatie Ingo Karkat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-Oct-2014 13:03 +0100, Bram Moolenaar wrote: Marco Hinz wrote: this might be yet another controversial patch, but it's asked for on IRC all the time. The problem is that the ~ markers (end of buffer) and parts of 'listchars' both use

Re: allow to vimgrep current buffer

2014-10-31 Fir de Conversatie Ingo Karkat
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-Oct-2014 12:42 +0100, Bram Moolenaar wrote: Zyx wrote: On October 29, 2014 10:54:38 PM EAT, Bram Moolenaar b...@moolenaar.net wrote: Christian wrote: On Di, 28 Okt 2014, Ingo Karkat wrote: Well, then perhaps a separate

omap ex commands are saved to command history after dot repeat

2014-10-31 Fir de Conversatie Jacob Niehus
Ex commands that have no keys typed aren't saved to command history. If an omap contains an ex command and the operation is repeated with '.', the ex command is saved to history because Vim considers the command to be typed because the period was typed. Simple example: vim -u NONE -i NONE -N