Hi Christian.
2014-07-01 22:00 GMT+04:00 Christian Brabandt cbli...@256bit.org:
Hi
Disclaimer: I haven't looked into matchaddpo() yet, but plan to use it in
several
plugins I maintain.
On Di, 01 Jul 2014, Bram Moolenaar wrote:
lcd wrote:
The initial motivation for adding the
Tomas Janousek wrote:
On Thu, May 22, 2014 at 06:14:46PM +0200, Bram Moolenaar wrote:
Patch 7.4.305
Problem:Making 'ttymouse' empty after the xterm version was requested
causes problems. (Elijah Griffin)
Solution: Do not check for DEC mouse sequences when the xterm version
Lcd wrote:
On 1 July 2014, Christian Brabandt cbli...@256bit.org wrote:
[...]
BTW: what happens to the highlighting after one changes the
buffer? E.g. if I add a matchaddpos() at line 5, column 5 and
afterwards add a line below 3, will then line 6, column 5 be
highlighted or line 5?
Hi,
I think this is a known bug that wasn't caught on the regression tests, as
mentioned in
http://stackoverflow.com/questions/18662065/cant-reset-global-mark-in-vim
This is how to reproduce it:
$ mv .viminfo{,.old}
$ vim -N -u NONE -U NONE
:h
mA
:marks
- mark A present
:qall
$ vim -N -u NONE
Montu wrote:
I think this is a known bug that wasn't caught on the regression
tests, as mentioned in
http://stackoverflow.com/questions/18662065/cant-reset-global-mark-in-vim
This is how to reproduce it:
$ mv .viminfo{,.old}
$ vim -N -u NONE -U NONE
:h
mA
:marks
- mark A present
Patch 7.4.348
Problem:When using J1 in 'cinoptions' a line below a continuation line
gets too much indent.
Solution: Fix parenthesis in condition.
Files: src/misc1.c
*** ../vim-7.4.347/src/misc1.c 2014-06-26 21:24:53.134537205 +0200
--- src/misc1.c 2014-07-02
Patch 7.4.349
Problem:When there are matches to highlight the whole window is redrawn,
which is slow.
Solution: Only redraw everything when lines were inserted or deleted.
Reset b_mod_xlines when needed. (Alexey Radkov)
Files: src/screen.c, src/window.c
***
Patch 7.4.350
Problem:Using C indenting for Javascript does not work well for a {} block
inside parenthesis.
Solution: When looking for a matching paren ignore one that is before the
start of a {} block.
Files: src/misc1.c, src/testdir/test3.in,
So, what is the problem? Check the help for :wviminfo for what it's
expected to do, it's not obvious.
I'm sorry if I wasn't clear. I was expecting that when I used `delmark` the
mark would disappear, but it is coming back after restarting Vim, i.e:
$ mv .viminfo{,.old}
$ vim -N -u NONE -U
Patch 7.4.351
Problem:sort() is not stable.
Solution: When the items are identical, compare the pointers.
Files: src/eval.c, src/testdir/test55.in, src/testdir/test55.ok
*** ../vim-7.4.350/src/eval.c 2014-06-25 17:31:04.942737863 +0200
--- src/eval.c 2014-07-02 18:52:19.102313288
Patch 7.4.352
Problem:With 'linebreak' a tab causes missing line break.
Solution: Count a tab for what it's worth also for shorter lines.
(Christian Brabandt)
Files: src/charset.c
*** ../vim-7.4.351/src/charset.c2014-06-25 14:39:35.098348584 +0200
---
On Monday, June 2, 2014 12:59:36 PM UTC-3, Ben Fritz wrote:
On Friday, May 30, 2014 9:09:19 AM UTC-5, David Fishburn wrote:
On Fri, May 30, 2014 at 9:46 AM, Christian Brabandt cbli...@256bit.org
wrote:
Hi Pedro!
On So, 25 Mai 2014, Pedro Ferrari wrote:
Patch 7.4.353
Problem:'breakindent' doesn't work with the 'list' option.
Solution: Make it work. (Christian Brabandt)
Files: runtime/doc/options.txt, src/charset.c, src/screen.c,
src/testdir/Make_amiga.mak, src/testdir/Make_dos.mak,
src/testdir/Make_ming.mak,
Ok, thank you very much!
--
--
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
---
You received this message because you are subscribed to the Google Groups
Hi.
In regexp operation,
\v and \V, in contrast with \c, \C, \m and \M, disable the preceding '$'
(end-of-line) atom.
This seems to be inconsequence.
matching end-of-line
echo 'hoge' =~# 'hoge$\m' | Expect 1, Result 1
echo 'hoge' =~# 'hoge$\M' | Expect 1, Result 1
echo 'hoge'
When the omnifunc provides extra info to be shown in the preview window (in
case preview is included in completeopt) there is a permanent focus switching
back and forth between the current window and the preview window, which
produces several annoying and very noticeable visual artifacts:
1)
Ozaki Kiichi wrote:
In regexp operation,
\v and \V, in contrast with \c, \C, \m and \M, disable the preceding '$'
(end-of-line) atom.
This seems to be inconsequence.
matching end-of-line
echo 'hoge' =~# 'hoge$\m' | Expect 1, Result 1
echo 'hoge' =~# 'hoge$\M' | Expect
On Wednesday, July 2, 2014 1:57:09 PM UTC-5, Ozaki Kiichi wrote:
Hi.
In regexp operation,
\v and \V, in contrast with \c, \C, \m and \M, disable the preceding '$'
(end-of-line) atom.
This seems to be inconsequence.
matching end-of-line
echo 'hoge' =~# 'hoge$\m' | Expect 1,
Hi,
Clang warns this after 7.4.338:
screen.c:3707:17: warning: expression which evaluates to zero treated as a null
pointer constant of type 'char_u *' (aka 'unsigned char *')
[-Wnon-literal-null-conversion]
p_extra = NUL;
^~~
Hi Carlos,
2014/7/3(Thu) 5:04:10 UTC+9 Carlos Pita:
When the omnifunc provides extra info to be shown in the preview window (in
case preview is included in completeopt) there is a permanent focus switching
back and forth between the current window and the preview window, which
produces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On July 3, 2014 6:59:52 AM GMT+03:00, Ben Fritz fritzophre...@gmail.com wrote:
On Wednesday, July 2, 2014 1:57:09 PM UTC-5, Ozaki Kiichi wrote:
Hi.
In regexp operation,
\v and \V, in contrast with \c, \C, \m and \M, disable the preceding
'$'
On Wednesday, July 2, 2014 11:49:38 PM UTC-5, ZyX wrote:
Shouldn't you need to escape the $ with a \ when using \V?
\V only *starts* the region. It does not affect the whole pattern.
Ah, you're right. I was expecting it to act like \c and \C:
22 matches
Mail list logo
