The command
0wincmd w
throws an error in the latest Vim version:
E16: Invalid range: 0wincmd w
Before, it simply stayed in the same window.
Is this a new feature or a bug?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are re
On Mon 12 Jan 2015 at 12:07:40AM -0800, Enno wrote:
> The command
>
> 0wincmd w
>
> throws an error in the latest Vim version:
>
> E16: Invalid range: 0wincmd w
>
> Before, it simply stayed in the same window.
> Is this a new feature or a bug?
It's being discussed here:
https://groups.google
Enno Nagel wrote:
> The command
>
> 0wincmd w
>
> throws an error in the latest Vim version:
>
> E16: Invalid range: 0wincmd w
>
> Before, it simply stayed in the same window.
> Is this a new feature or a bug?
There is no window with the number zero, so the error is correct.
Is this breaki
echo $
This occur E15, but eval('$') doesn't.
diff -r ab36689121ad src/eval.c
--- a/src/eval.cWed Dec 17 21:00:49 2014 +0100
+++ b/src/eval.cSat Jan 10 01:31:54 2015 +0900
@@ -7867,7 +7867,10 @@
if (evaluate)
{
if (len == 0)
- return FAIL; /* can't be a
Hello, list
I wrote a patch to correct some problems with continuation lines inside
if clauses.
In the current version of the code, the next snippet was indented as
follows:
do i=1,end
if (condition1 .AND. &
condition2) then
do something
end if
end do
In the proposed patch, I propos
I'm thinking range('a', 'c') should return ['a', 'b', 'c'].
How about this?
https://gist.github.com/mattn/820801be0c2f5ee2d008
--
--
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://ww
Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
> Enno Nagel wrote:
>
> > The command
> >
> > 0wincmd w
> >
> > throws an error in the latest Vim version:
> >
> > E16: Invalid range: 0wincmd w
> >
> > Before, it simply stayed in the same window.
> > Is this a new feature or
Am 2015-01-11 15:49, schrieb Dominique Pellé:
On Sun, Jan 11, 2015 at 2:29 PM, Dominique Pellé wrote
Hi
I noticed a bug in Vim-7.4.567 with syntax highlighting of
tabs when using the conceal feature. How to reproduce:
$ vim -N -u NONE \
-c 'syn on' \
-c 'set cole=2 list lcs=tab:»·' \
-c
On Mon, Jan 12, 2015 at 9:52 AM, Enno wrote:
> Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
> > Enno Nagel wrote:
> >
> > > The command
> > >
> > > 0wincmd w
> > >
> > > throws an error in the latest Vim version:
> > >
> > > E16: Invalid range: 0wincmd w
> > >
> > > Before, i
Le lundi 12 janvier 2015 17:23:37 UTC+1, David Fishburn a écrit :
> On Mon, Jan 12, 2015 at 9:52 AM, Enno wrote:
> Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
>
> > Enno Nagel wrote:
>
> >
>
> > > The command
>
> > >
>
> > > 0wincmd w
>
> > >
>
> > > throws an error in
Yasuhiro Matsumoto wrote:
> echo $
>
> This occur E15, but eval('$') doesn't.
>
> diff -r ab36689121ad src/eval.c
> --- a/src/eval.c Wed Dec 17 21:00:49 2014 +0100
> +++ b/src/eval.c Sat Jan 10 01:31:54 2015 +0900
> @@ -7867,7 +7867,10 @@
> if (evaluate)
> {
> if (len
Hello:
I've found something peculiar. When I put :echomsg "GOT HERE" into
autoload/netrw.vim just before the "if v:version < 704..." test (line#25
with v153), no output appears. No output appears with a subsequent
:messages.
This difficulty means that an echomsg will show no output inside that
Enno Nagel wrote:
> Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
> > Enno Nagel wrote:
> >
> > > The command
> > >
> > > 0wincmd w
> > >
> > > throws an error in the latest Vim version:
> > >
> > > E16: Invalid range: 0wincmd w
> > >
> > > Before, it simply stayed in the
Yasuhiro Matsumoto wrote:
> I'm thinking range('a', 'c') should return ['a', 'b', 'c'].
>
> How about this?
>
> https://gist.github.com/mattn/820801be0c2f5ee2d008
'a' is not the character 'a', it's a string starting with 'a'.
You can already do: range(char2nr('a'), char2nr('c'))
It's more ve
Charles Campbell wrote:
> I've found something peculiar. When I put :echomsg "GOT HERE" into
> autoload/netrw.vim just before the "if v:version < 704..." test (line#25
> with v153), no output appears. No output appears with a subsequent
> :messages.
>
> This difficulty means that an echomsg wi
On 22:26 Mon 12 Jan , Bram Moolenaar wrote:
>
> Enno Nagel wrote:
>
> > Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
> > > Enno Nagel wrote:
> > >
> > > > The command
> > > >
> > > > 0wincmd w
> > > >
> > > > throws an error in the latest Vim version:
> > > >
> > > >
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 313 by fritzoph...@gmail.com: pedit changes cursor position when
BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
What steps will reproduce the problem?
1. Start Vim with gvim -N -u NONE -i NONE
Comment #4 on issue 184 by josh.end...@gmail.com: Setting (paste) input
mode after setting ruler causes ruler to hide
https://code.google.com/p/vim/issues/detail?id=184
Curious as well. What is the technical explanation for why "set ruler"
interferes with paste mode?
--
You received this
Comment #1 on issue 313 by vega.ja...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
Are you sure the description of what you're seeing is correct? The
behavior I'm seeing is that the cursor is still on the last l
I know what i want can do with map(range(char2nr('a'), char2nr('z')),
'nr2char(v:val)').
But it's too long. I think.
--
--
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/
Comment #2 on issue 313 by fritzoph...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
Yes. On my machine, after the :pedit %, I see the copyright notice at the
top of my 1400-line file, in the bottom window. In the
Comment #3 on issue 313 by fritzoph...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
Same behavior (bottom window set to cursor on line 1, top window a preview
window set to cursor on last line where it started) i
https://code.google.com/p/vim/source/detail?r=b3bc99b909c321374570ac7a7e57ed78e85e87d4
Next version should be 7.4-28 ?
--
--
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
23 matches
Mail list logo
