Re: strange stray unicode character on the second line of all files

On Sat, Jan 26, 2019 at 2:19 PM Bram Moolenaar wrote: > > Aryeh Friedman wrote: > > > On Sat, Jan 26, 2019 at 9:13 AM Bram Moolenaar > wrote: > > > > > > Aryeh Friedman wrote: > > > > > > > For some odd reason (bug?) a stray unprintable unicode character > appear= > > s > > > > several spaces

Re: strange stray unicode character on the second line of all files

Aryeh Friedman wrote: > On Sat, Jan 26, 2019 at 9:13 AM Bram Moolenaar wrote: > > > > Aryeh Friedman wrote: > > > > > For some odd reason (bug?) a stray unprintable unicode character appear= > s > > > several spaces over on the second line of every file I edit (even when > > the > > > second

Re: strange stray unicode character on the second line of all files

On Sat, Jan 26, 2019 at 9:13 AM Bram Moolenaar wrote: > > Aryeh Friedman wrote: > > > For some odd reason (bug?) a stray unprintable unicode character appears > > several spaces over on the second line of every file I edit (even when > the > > second line is nothing more then a new line): > > >

Re: (editor/vim) Re: strange stray unicode character on the second line of all files

On Sat, Jan 26, 2019 at 11:08 AM Adam Weinberger wrote: > On Sat, Jan 26, 2019 at 9:00 AM Aryeh Friedman > wrote: > > > > > > > > On Sat, Jan 26, 2019 at 10:56 AM Aryeh Friedman < > aryeh.fried...@gmail.com> wrote: > >> > >> > >> > >> On Sat, Jan 26, 2019 at 9:54 AM Adam Weinberger > wrote: >

Re: (editor/vim) Re: strange stray unicode character on the second line of all files

On Sat, Jan 26, 2019 at 10:56 AM Aryeh Friedman wrote: > > > On Sat, Jan 26, 2019 at 9:54 AM Adam Weinberger wrote: > >> On Sat, Jan 26, 2019 at 1:59 AM Aryeh Friedman >> wrote: >> > >> > Note I have added the maintainer of the vim port on FreeBSD to the To >> header for reasons given in the

Re: (editor/vim) Re: strange stray unicode character on the second line of all files

On Sat, Jan 26, 2019 at 9:54 AM Adam Weinberger wrote: > On Sat, Jan 26, 2019 at 1:59 AM Aryeh Friedman > wrote: > > > > Note I have added the maintainer of the vim port on FreeBSD to the To > header for reasons given in the body of the reply > > > > On Fri, Jan 25, 2019 at 6:43 PM Tony

Re: strange stray unicode character on the second line of all files

Aryeh Friedman wrote: > For some odd reason (bug?) a stray unprintable unicode character appears > several spaces over on the second line of every file I edit (even when the > second line is nothing more then a new line): > > // src/java/specmed/devinv/DevInvUtil.java > � <-- The stray

Re: CTRL-F Setting

> I realize this topic is kind of old but I think it is important. > > Remapping basic vim functionality (such as Ctrl-F) should NEVER be > done by default. At a minimum, mswin.vim should not be setup to be > sourced by default (with notes on how to add it if you want the > Windows

Re: Strange Characters in TOC window when using vim-pandoc plugin

On Saturday, January 26, 2019 at 7:14:54 PM UTC+8, Joey Ling wrote: > When I execute the :TOC command in Vim, TOC window apperars in the left, but > the headers show strange characters like ... > > Why and how to fix it? If I put a between # and words in the headers, the disappears, like

Strange Characters in TOC window when using vim-pandoc plugin

When I execute the :TOC command in Vim, TOC window apperars in the left, but the headers show strange characters like ... Why and how to fix it? -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more

(editor/vim) Re: strange stray unicode character on the second line of all files

Note I have added the maintainer of the vim port on FreeBSD to the To header for reasons given in the body of the reply On Fri, Jan 25, 2019 at 6:43 PM Tony Mechelynck < antoine.mechely...@gmail.com> wrote: > On Sat, Jan 26, 2019 at 12:31 AM Aryeh Friedman > wrote: > > > > Forgot to mention