As promised I did some other tests. First I can say the new patch fixed the
error I could reproduce with my example. It also fixed EasyAlign, BUT
CoffeeCompile is still giving the same error (Invalid Address)
Anyway, here' a screenshot I took before updating vim:
http://oi61.tinypic.com/2cr7plw.
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 290 by enno.na...@gmail.com: gVim does not jump to given
linennumber if already at end of file
https://code.google.com/p/vim/issues/detail?id=290
What steps will reproduce the problem?
1. gvim +G file.txt
2. gvim +{linenumb
In editexisting.vim from 2013 Feb 24, can the splits occurring at line number
106 and below be made optional ? That is, use either edit or split by setting a
global variable.
The concerned code is:
if winnr > 0
exe winnr . "wincmd w"
elseif exists('*fnameescape')
exe "split " . fna
Vim crashes with list range assign.
Steps to reproduce:
$ vim -u NONE
:let x = [0]
:let x[:] = [1, 2]
Vim: Caught deadly signal SEGV
Vim: Finished.
Please check the following patch.
diff -r 4604a182f04c src/eval.c
--- a/src/eval.cSun Nov 30 22:51:06 2014 +0100
+++ b/src/eval.c
Comment #1 on issue 290 by enno.na...@gmail.com: gVim does not jump to
given linennumber if already at end of file
https://code.google.com/p/vim/issues/detail?id=290
Well, the confusion is that gvim +... file.txt waits for a normal mode
command and not for an exe command as the Vim doc says
Comment #2 on issue 290 by benjamin...@rockwellcollins.com: gVim does not
jump to given linennumber if already at end of file
https://code.google.com/p/vim/issues/detail?id=290
I don't understand your comment. gvim +... file.txt uses the supplied
command as an ex command, not a normal-mode
Comment #11 on issue 287 by chrisbr...@googlemail.com: Newline substitution
behaviour
https://code.google.com/p/vim/issues/detail?id=287
Vim 7.4 reported " substitutions on 1 line", vim 7.4.232
reports " substitutions on lines" Which I
personally think is correct, since this is the number o
Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to
given linennumber if already at end of file
https://code.google.com/p/vim/issues/detail?id=290
Vim 7.4 works correctly with +[] here (if no number is given, Vim
jumps to the last line number). I cannot reproduce the
Hi,
I have a small project that looks at logging the names of the files that have
been edited by vi.
Can someone kindly point out which part of the code handle files?
thanks
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are r
On 2014-12-01, jy yap wrote:
> Hi,
>
> I have a small project that looks at logging the names of the
> files that have been edited by vi.
>
> Can someone kindly point out which part of the code handle files?
This can be done with a plugin. You don't need to modify Vim's
source code.
If you wan
Using a Vim that is built to be able to access X's PRIMARY and CLIPBOARD
selections (i.e., "* and "+), performing “:let &term=&term” causes Vim
to "forget" that it knows how to access those registers.
This is because set_termname() ends up calling clip_init(), which sets
owned = FALSE on both VimC
11 matches
Mail list logo
