Re: Escape sequences printed to the console when starting Gvim 8.1

After reading here, I went back to the 18.04 install, and updated vim to the latest, and the problem does not occur now. Regards, John Little -- -- 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,

Re: Escape sequences printed to the console when starting Gvim 8.1

On Thursday, 7 January 2021 at 16:59:18 UTC Bram Moolenaar wrote: > > Dominique wrote: > > > I recall that for recent vim, terminals such as xfce4-terminal > > and gnome-terminal (maybe others) in Ubuntu-18.04 are too > > old and Vim can output spurious codes on the terminal, > > It hapens

Re: Getting/setting mark/cursor position using character index instead of byte index

Yegappan wrote: > > > The getpos(), col() and getcurpos() functions currently return the byte > > > index > > > in a line. The setpos() and cursor() functions use the byte index to > > > position > > > the cursor or to set a mark. > > > > > > The language server protocol uses character index

Re: Getting/setting mark/cursor position using character index instead of byte index

Hi Bram, On Thu, Jan 7, 2021 at 1:04 PM Bram Moolenaar wrote: > > Yegappan wrote: > > > The getpos(), col() and getcurpos() functions currently return the byte > > index > > in a line. The setpos() and cursor() functions use the byte index to > > position > > the cursor or to set a mark. > > >

Re: Getting/setting mark/cursor position using character index instead of byte index

Yegappan wrote: > The getpos(), col() and getcurpos() functions currently return the byte > index > in a line. The setpos() and cursor() functions use the byte index to > position > the cursor or to set a mark. > > The language server protocol uses character index instead of byte index > in a

Patch 8.2.2311

Patch 8.2.2311 Problem:Vim9: cannot assign to a variable that shadows a command modifier. Solution: Check for assignment after possible command modifier. (closes #7632) Files: src/vim9compile.c, src/ex_docmd.c, src/testdir/test_vim9_assign.vim ***

Patch 8.2.2310

Patch 8.2.2310 Problem:Vim9: winsaveview() return type is too generic. Solution: use dict instead of dict. (closes #7626) Files: src/evalfunc.c, src/testdir/test_vim9_builtin.vim *** ../vim-8.2.2309/src/evalfunc.c 2021-01-06 21:59:35.174021934 +0100 --- src/evalfunc.c

Patch 8.2.2309

Patch 8.2.2309 Problem:0o777 not recognized as octal. Solution: Use vim_isodigit(). (Ken Takata, closes #7633, closes #7631) Files: src/charset.c, src/testdir/test_eval_stuff.vim *** ../vim-8.2.2308/src/charset.c 2020-06-10 14:16:30.098988403 +0200 --- src/charset.c

Patch 8.2.2308

Patch 8.2.2308 Problem:Vim9: no error when assigning lambda to funcref without return value. Solution: Default return value to "any". (closes #7629) Files: src/userfunc.c, src/vim9compile.c, src/testdir/test_vim9_assign.vim, src/testdir/test_vim9_func.vim ***

Re: [vim/vim] netrw's "gx" functionality doesn't open URLs anymore in macOS (#4738)

K.Takata (Vim Github Repository) wrote: It seems that my patch has been (partly) included in the prerelease version: http://www.drchip.org/astronaut/vim/#NETRW. If @cecamp thinks it is ready for releasing, he will send the files to Bram. But he doesn't think it is

Getting/setting mark/cursor position using character index instead of byte index

Hi all, The getpos(), col() and getcurpos() functions currently return the byte index in a line. The setpos() and cursor() functions use the byte index to position the cursor or to set a mark. The language server protocol uses character index instead of byte index in a line. I see that the

Re: Escape sequences printed to the console when starting Gvim 8.1

Dominique wrote: > Bram Moolenaar wrote: > > > Philip Pemberton wrote: > > > > > I've just solved a packaging issue on the machine, and Apt has pulled down > > > Vim 8.2.1897, with the same issue. Console output below: > > > > > [...] > > > > > philpem@cheetah:~$ gvim > > > [>4;m

Re: Escape sequences printed to the console when starting Gvim 8.1

Bram Moolenaar wrote: > Philip Pemberton wrote: > > > I've just solved a packaging issue on the machine, and Apt has pulled down > > Vim 8.2.1897, with the same issue. Console output below: > > > [...] > > > philpem@cheetah:~$ gvim > > [>4;m [>4;2mphilpem@cheetah:~$ gvim > > [>4;m

Patch 8.2.2307

Patch 8.2.2307 Problem:A shell command in the vimrc causes terminal output. Solution: Do not call starttermcap() after a shell command if the termcap wasn't active before. Files: src/ex_cmds.c *** ../vim-8.2.2306/src/ex_cmds.c 2021-01-04 12:41:49.503891371 +0100

Re: Escape sequences printed to the console when starting Gvim 8.1

Philip Pemberton wrote: > I've just solved a packaging issue on the machine, and Apt has pulled down > Vim 8.2.1897, with the same issue. Console output below: > [...] > philpem@cheetah:~$ gvim > [>4;m [>4;2mphilpem@cheetah:~$ gvim > [>4;m [>4;2mphilpem@cheetah:~$ You probably have a

Re: Escape sequences printed to the console when starting Gvim 8.1

On Mi, 06 Jan 2021, Philip Pemberton wrote: > I've just solved a packaging issue on the machine, and Apt has pulled down > Vim 8.2.1897, with the same issue. Console output below: > philpem@cheetah:~$ gvim > [>4;m [>4;2mphilpem@cheetah:~$ gvim > [>4;m [>4;2mphilpem@cheetah:~$ Looks a bit like