2017年5月16日火曜日 21時14分32秒 UTC+9 itc...@hatena.ne.jp:
> 2017年5月16日火曜日 14時36分04秒 UTC+9 Bram Moolenaar:
> > > 2017年5月11日木曜日 21時52分48秒 UTC+9 Bram Moolenaar:
> > > > Ken Hamada wrote:
> > > >
> > > > > Hi list, I noticed that E16 occurs with regexp.
> > > > >
> > > > > set re=1
> > > > > echo '' =~# '[\
2017年5月16日火曜日 14時36分04秒 UTC+9 Bram Moolenaar:
> > 2017年5月11日木曜日 21時52分48秒 UTC+9 Bram Moolenaar:
> > > Ken Hamada wrote:
> > >
> > > > Hi list, I noticed that E16 occurs with regexp.
> > > >
> > > > set re=1
> > > > echo '' =~# '[\uff-\uf0]'
> > > > E16: Invalid range
> > > > echo '' =~# '[\u3000-
2017年5月11日木曜日 21時52分48秒 UTC+9 Bram Moolenaar:
> Ken Hamada wrote:
>
> > Hi list, I noticed that E16 occurs with regexp.
> >
> > set re=1
> > echo '' =~# '[\uff-\uf0]'
> > E16: Invalid range
> > echo '' =~# '[\u3000-\u4000]'
> > E16: Invalid range
> >
> > I think this is unintuitive error message
On Thursday, May 11, 2017 at 2:17:40 PM UTC+9, itchyny wrote:
> Hi list, I noticed that E16 occurs with regexp.
>
> set re=1
> echo '' =~# '[\uff-\uf0]'
> E16: Invalid range
Oops, I mean
echo '' =~# '[\xff-\xf0]'
--
--
You received th
2017年5月11日木曜日 14時17分40秒 UTC+9 itchyny:
> Hi list, I noticed that E16 occurs with regexp.
>
> set re=1
> echo '' =~# '[\uff-\uf0]'
Oops, I mean:
echo '' =~# '[\xff-\xf0]'
--
--
You received this message from the "vim_dev" mai
Hi list, I noticed that E16 occurs with regexp.
set re=1
echo '' =~# '[\uff-\uf0]'
E16: Invalid range
echo '' =~# '[\u3000-\u4000]'
E16: Invalid range
I think this is unintuitive error message because E16 reminds us the range of
commands (for example :0buffer). So I suggest two exclusive options:
Hi list, this is a small patch to grab the column number of the first non-white
character in the current line. I wrote because found in the todo list.
https://gist.github.com/itchyny/22e9871b15eec445ddb8c3a7451222af
Regards,
Ken Hamada (aka itchyny on GitHub)
--
--
You received this message
On Tuesday, December 13, 2016 at 1:26:30 AM UTC+9, Ozaki Kiichi wrote:
> It is better to add it for an unit test.
>
> maka -C src test_fillchars
Thank you for your notice, it's surely useful.
Here is the latest patch.
https://gist.github.com/itchyny/936f5c7e7f6396bf2f6afbe2462
> Thank you Bram. I've got the point.
> How about this patch?
> I noticed the note in syntax.txt but still believe that the patch solves the
> strange behavior
> that most people will not configure what's going on until look into the
> source code.
>
Sorry, there's no need to add the test in M
aststatus=2 statusline=\ fillchars=stl:_,stlnc:_ nosplitright
+ highlight StatusLine ctermbg=8 ctermfg=7 cterm=NONE guibg=#808080
guifg=#c0c0c0 gui=NONE
+ highlight StatusLineNC ctermbg=8 ctermfg=7 cterm=NONE guibg=#808080
guifg=#c0c0c0 gui=NONE
+ only! | vnew
+ redrawstatus!
+ call assert_equ
return '^';
What do you think?
Sincerely,
Ken Hamada (aka itchyny on GitHub)
--
--
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
---
Yo
2016年7月30日土曜日 3時51分08秒 UTC+9 Bram Moolenaar:
> Patch 7.4.2117
> Problem:Deleting an augroup that still has autocmds does not give a
> warning. The next defined augroup takes its place.
> Solution: Give a warning and prevent the index being used for another group
> nam
I additionally submit another test case.
let Y = {f -> (({x -> f ({y -> x(x)(y)})}) ({x -> f ({y -> x(x)(y)})}))}
let Fact = {f -> {x -> (x == 0 ? 1 : x * f(x - 1))}}
echo Y(Fact)(5)
I expect this script prints 120 but I got E110: Missing ')' in 7.4.2049 (and
also with the experimental patch).
I
On Sunday, July 17, 2016 at 2:56:44 AM UTC+9, Bram Moolenaar wrote:
> Ken Hamada wrote:
>
> > Hi Bram and Ken Takata.
> >
> > I think there is some problem in variable substitution of lambda function.
> >
> > echo ({y -> ({x -> x(y)(10)})({y -> y})})({z -> z})
> >
> > yields an error `E121: Und
Sorry, I got E117, not E121.
--
--
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 Grou
Hi Bram and Ken Takata.
I think there is some problem in variable substitution of lambda function.
echo ({y -> ({x -> x(y)(10)})({y -> y})})({z -> z})
yields an error `E121: Undefined variable: y`. I expect this expression yields
10. I tested on Vim 7.4.2048.
JavaScript:
(function(y){ return (
On Friday, July 31, 2015 at 11:07:24 PM UTC+9, h_east wrote:
> Hi itchyny,
>
> 2015-7-26(Sun) 20:46:05 UTC+9 itchyny:
> > Vim warns E749 on switching to a buffer which used to be checked diff.
> >
> > How to reproduce.
> > 1. vim -u NONE -N
> > 2. :e test |
Vim warns E749 on switching to a buffer which used to be checked diff.
How to reproduce.
1. vim -u NONE -N
2. :e test | diffthis
3. :vnew test2 | diffthis
4. :e test3
5. :buffer #
Error message
E749: empty buffer
What I expect
Vim opens the test2 with no error message.
Environment
Vim 7.4.796
V
Bram, thank you so much for including the patch.
Higashi-san, thank you so much for the patch fixing the behaviour of tabmove,
as well as the document.
Using the latest version for a while, I noticed that the behaviour of tabm $ is
a very intuitive.
... so much that I confirmed for several times
r the patch.
On Friday, March 20, 2015 at 9:51:53 PM UTC+9, Bram Moolenaar wrote:
> Hirohito Higashi wrote:
>
> > Hi Bram and itchyny and List,
> >
> > 2015/3/15(Sun) 7:48:01 UTC+9 Bram Moolenaar:
> > > Hirohito Higashi wrote:
> > >
> > > >
bility. Some
users may
use `:tabmove` in order to move the tab to the last.
By the way, :tabmove 0 and :0tabmove behaves the same, sometimes I mistake as
:tabmove $. This command now throws invalid argument.
itchyny
--
--
You received this message from the "vim_dev" maillist.
Do not top-
you for your patch!
I checked your patch and recompiled to find that the behaviour of `:-tabmove`
and
`:+tabmove` are fixed. Great work and I hope it merged.
itchyny
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are re
Hello, all.
I think that there are some problems for :tabmove. Firstly, see the document
(:h :tabmove).
:tabm[ove] [N] *:tabm* *:tabmove*
:[N]tabm[ove]
Move the current tab page to after tab page N. Use zero to
make the cur
On Saturday, February 7, 2015 at 10:39:05 PM UTC+9, Bram Moolenaar wrote:
> Itchyny wrote:
>
> > The option 'incsearch' just jumps to the first matching place and
> > highlights it.
> > We then press enter, all the matches are get highlighted (if we set
> >
= do_search(NULL, firstc, ccline.cmdbuff, count,
- SEARCH_KEEP + SEARCH_OPT + SEARCH_NOOF + SEARCH_PEEK,
+ SEARCH_OPT + SEARCH_NOOF + SEARCH_PEEK,
#ifdef FEAT_RELTIME
&tm
Regards, itchyny.
Thanks.
--
--
You received this message from the "vim_d
On Sunday, November 30, 2014 1:38:09 AM UTC+9, Marcin Szamotulski wrote:
> On 22:14 Fri 28 Nov , Bram Moolenaar wrote:
> >
> > Itchyny wrote:
> >
> > > Bram, the is always 1 (probably after this patch).
> > >
> > > :command! Test ech
Bram, the is always 1 (probably after this patch).
:command! Test echo
try :Test and it always echoes 1.
--
--
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
On Tuesday, July 8, 2014 3:43:00 PM UTC+9, Brook Hong wrote:
> It will be useful, if there is a function to get a list of all variables with
> specific type.
>
> For example,
>
> let g:foo='foo'
> let g:bar='bar'
>
>
> call listvars('g')
> // return ['foo', 'bar']
Try :echo keys(g:).
--
--
To reproduce
vim -u NONE -N
500ia^
>>
set wrap breakindent
set breakindentopt=shift:10
hlhlhlwbwb
x
Problem
The indentation is not updated soon after we change breakindentopt.
Expected behaviour
The indentation is updated soon.
Environment
Vim 7.4 1-345
--
--
You received this message from th
To reproduce
vim -u NONE -N
500ia^
:set breakindent
>>
>>
>>
XXX
Problem
The second and the following lines are kept indented.
Expected behaviour
The indent level follows that of the first line.
Environment
On Vim 7.4 1-340, Ubuntu
--
--
You received this message from the "vim_dev" maillist.
> Can you check this: All places where sed is used in src/installman.sh,
>
> prepend LC_ALL=C for every sed command (there are three).
>
Right. Prepending LC_ALL=C for the three places fixes the "sed: RE error:
illegal byte sequence" errors.
--
--
You received this message from the "vim_dev"
x27;t know that which shell supports modifying a variable temporarily.
Reference
+ http://stackoverflow.com/questions/19242275/
+ http://stackoverflow.com/questions/11287564/
(Sorry for choosing stackoverflow as references, but it actually works.)
On Sunday, June 22, 2014 7:43:19 PM UTC+9, B
# Command
$ sudo make install
# On
Mac OS X
Vim the latest
# Produces sed errors
/bin/sh ./installman.sh install /usr/local/share/man/fr/man1 "-fr"
/usr/local/share/vim /usr/local/share/vim/vim74 /usr/local/share/vim
../runtime/doc 644 vim vimdiff evim
installing /usr/local/share/man/fr/m
Thank you so much.
On Tuesday, June 10, 2014 5:39:34 AM UTC+9, Charles Campbell wrote:
> itchyny wrote:
>
> > let m = 5
>
> > let y = 20 * (m / 4) + m / 4
>
> > let z = 10
>
> > for i in range(10)
>
> >echo i
>
> > endfor
>
Hi, list.
This is a bug in syntax/vim.vim.
Consider we are editing a Vim script file. (setl ft=vim)
When we use two slashes in a line, the syntax is broken.
For example:
let [a, b] = [winheight(0) / 2, winwidth(0) / 2]
'/ 2, winwidth(0) /' is considered as a string.
It's tolerable if it does no
On Wednesday, February 6, 2008 5:44:23 AM UTC+9, Bram Moolenaar wrote:
> Jan Christoph Ebersbach wrote:
>
> > Hi,
> >
> > I set the following options to see the current status of paste:
> >
> > set pastetoggle=
> > set statusline=%{&paste}
> >
> > It works perfectly except that a single press o
On Saturday, July 6, 2013 1:39:03 AM UTC+9, Charles Campbell wrote:
> Please try syntax/vim.vim v7.3-26 , available at my website at
>
> http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM .
>
>
>
> The problem: s:Xxxx was permitted (old rules for what was allowed to be
>
> a function
Hi list. There is a problem in vim.vim for |command-completion-customlist|.
-
command! -nargs=+ -complete=customlist,s: X call s:x()
-
The above example is looks like:
https://f.cloud.github.com/assets/375258/752414/fb5dee78-e543-11e2-8fcd-b9ea89846ad6.png
Expected:
https://f.c
38 matches
Mail list logo
