On Tue, Aug 4, 2020 at 8:01 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > According to ":h +builtin_terms", there are no builtin terminals in
> > Tiny or Small (I think this is a documentation error), some in Normal,
> > and all in Big and Huge. The following, however, is what ":set
> > term=xx
> But how is `getbufinfo({expr})[0].lnum` userful? I honestly don't
> understand the purpose of it since the buffer needs to be focused.
> Isn't it the same as `line('.')`?
Try editing the buffer in the current window and then switching to
another buffer, then it works as you expect.
If the buf
Patch 8.2.1364
Problem:Invalid memory access when searching for raw string.
Solution: Check for delimiter match before following quote. (closes #6578)
Files: src/search.c
*** ../vim-8.2.1363/src/search.c2020-06-12 22:59:07.270097188 +0200
--- src/search.c2020-08-04 21
Patch 8.2.1363
Problem:Test trying to run terminal when it is not supported.
Solution: Check if Vim can be run in a terminal.
Files: src/testdir/test_termcodes.vim
*** ../vim-8.2.1362/src/testdir/test_termcodes.vim 2020-08-04
20:17:28.491204565 +0200
--- src/testdir/test_termco
Patch 8.2.1362
Problem:Last entry of ":set term=xxx" overwritten by error message when
'cmdheight' is two or more. (Tony Mechelynck)
Solution: Output extra line breaks.
Files: src/term.c, src/testdir/test_termcodes.vim
*** ../vim-8.2.1361/src/term.c 2020-07-14 23:02:38.1
Jay Sitter wrote:
> Jules Wang has asked me to take over as maintainer of the CSS syntax =
> file. Attaching a small patch here.
I'll include it, thanks.
--
Support your right to bare arms! Wear short sleeves!
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///
Tony wrote:
> According to ":h +builtin_terms", there are no builtin terminals in
> Tiny or Small (I think this is a documentation error), some in Normal,
> and all in Big and Huge. The following, however, is what ":set
> term=xxx" gives me in Console mode in each build:
>
> Tiny with no GUI:
>
According to ":h +builtin_terms", there are no builtin terminals in
Tiny or Small (I think this is a documentation error), some in Normal,
and all in Big and Huge. The following, however, is what ":set
term=xxx" gives me in Console mode in each build:
Tiny with no GUI:
builtin_ansi
builtin_x
Patch 8.2.1361
Problem:Error for white space after expression in assignment.
Solution: Skip over white space. (closes #6617)
Files: src/eval.c, src/testdir/test_expr.vim
*** ../vim-8.2.1360/src/eval.c 2020-08-03 22:39:05.902971252 +0200
--- src/eval.c 2020-08-04 15:48:25.930152983
Jules Wang wrote:
> Jay is a very active developer in css syntax file repo,
> https://github.com/JulesWang/css.vim. I recommend him as the new
> maintainer of the css syntax file. I have maintained this file for 8
> years, it is time to take a break :-)
>
> some suggestions for Jay:
> 1. ta
On Mo, 03 Aug 2020, Jay Sitter wrote:
> Jules Wang has asked me to take over as maintainer of the CSS syntax file.
> Attaching a small patch here.
Thanks for taking over. Since I just stumbled over this (neovim) bug
here: https://github.com/neovim/neovim/issues/12714 can you please have
a lo
Jay is a very active developer in css syntax file repo,
https://github.com/JulesWang/css.vim. I recommend him as the new
maintainer of the css syntax file. I have maintained this file for 8
years, it is time to take a break :-)
some suggestions for Jay:
1. take small steps
2. respect stability
Jules Wang has asked me to take over as maintainer of the CSS syntax file.
Attaching a small patch here.
Thanks,
Jay
--
--
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/
Jules Wang has asked me to take over as maintainer of the CSS syntax file.
Attaching a small patch here.
Thanks,
Jay
--
--
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/
14 matches
Mail list logo
