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 ins

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 l

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 variou