On 03/19/2015 01:44, John Little wrote:
but my reading of syntax/sh.vim suggests this is no longer quite true.
Thanks, 'let g:is_posix = 1' fixed it.
Yuri
--
--
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
Hi Roland,
2015/3/19(Thu) 21:03:17 UTC+9 Roland Eggner:
On 2015-03-18 Wednesday at 00:54 -0700 h_east wrote:
(9) :.-tabm [1] 2 3 4 5 Move to the left
Oops. It was typo. Correctly is here.
(9) :.-tabm [2] 1 3 4 5 Move to the left
I represent specification description
On Thursday, March 19, 2015 at 6:58:53 PM UTC+13, Yuri wrote:
OS is FreeBSD, vim-7.4.657, #!/bin/sh is Bourne shell,
IIRC arithmetic evaluation $(()) and process execution using $() were not in
the original Bourne shell, they are POSIX features (that came first from the
Korn shell I think).
On 2015-03-18 Wednesday at 00:54 -0700 h_east wrote:
(9) :.-tabm [1] 2 3 4 5 Move to the left
Oops. It was typo. Correctly is here.
(9) :.-tabm [2] 1 3 4 5 Move to the left
I represent specification description below.
$ vim -N -u NONE -p A B C D E -c tabnext 3
A B
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 344 by TruSktr: Inconsistency with virtualedit=onemore $ and g$
in NORMAL vs VISUAL.
https://code.google.com/p/vim/issues/detail?id=344
With set virtualedit=onemore, $ takes me to the last character in NORMAL,
not past
Hi Nazri!
On Fr, 13 Mär 2015, Nazri Ramliy wrote:
On Fri, Mar 13, 2015 at 3:58 AM, Christian Brabandt cbli...@256bit.org
wrote:
Also further testing shows, this seems only to happen, as long as the
number column is smaller than the showbreak chars. I can't explain that.
I think it
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 343 by rym...@gmail.com: Goog
https://code.google.com/p/vim/issues/detail?id=343
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you
Updates:
Status: Duplicate
Mergedinto: 340
Comment #3 on issue 341 by chrisbr...@googlemail.com: Google Code will close
https://code.google.com/p/vim/issues/detail?id=341
(No comment was entered for this change.)
--
You received this message because this project is configured
There has been a blog post about analyzing source code of vim with the
PVS-Studio application. They found several problems and mentioned them
here:
http://www.viva64.com/en/b/0311/
I asked them to provide the complete list so we can fix actual problems.
Best,
Christian
--
Riechen streng des
Updates:
Status: Duplicate
Mergedinto: 341
Comment #2 on issue 343 by chrisbr...@googlemail.com: Goog
https://code.google.com/p/vim/issues/detail?id=343
Yes, this is being discussed on the vim-dev list already. See also issues
342 and 341. Closing
--
You received this
Comment #2 on issue 341 by chrisbr...@googlemail.com: Google Code will close
https://code.google.com/p/vim/issues/detail?id=341
Issue 343 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may
Comment #3 on issue 340 by chrisbr...@googlemail.com: Migrate away from
Google Code?:
https://code.google.com/p/vim/issues/detail?id=340
Issue 341 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this
Comment #1 on issue 343 by rym...@gmail.com: Goog
https://code.google.com/p/vim/issues/detail?id=343
ACK! Stupid Google Code! The title's supposed to be Google Code is Dying.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
--
You received this message because this
13 matches
Mail list logo
