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 <adamw@freebsd.org> wrote:

On Sat, Jan 26, 2019 at 9:00 AM Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
>
>
>
> On Sat, Jan 26, 2019 at 10:56 AM Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
>>
>>
>>
>> On Sat, Jan 26, 2019 at 9:54 AM Adam Weinberger <adamw@freebsd.org> wrote:
>>>
>>> On Sat, Jan 26, 2019 at 1:59 AM Aryeh Friedman <aryeh.friedman@gmail.com> 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 Mechelynck <antoine.mechelynck@gmail.com> wrote:
>>> >>
>>> >> On Sat, Jan 26, 2019 at 12:31 AM Aryeh Friedman
>>> >> <aryeh.friedman@gmail.com> wrote:
>>> >> >
>>> >> > Forgot to mention that hitting ^R or ^L will clear the character from the screen
>>> >> >
>>> >> > On Fri, Jan 25, 2019 at 4:40 AM Aryeh Friedman <aryeh.friedman@gmail.com> 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 unicode character
>>> >> >> Here is the output for cat -e of the first two lines of the same file:
>>> >> >>
>>> >> >> // src/java/specmed/devinv/DevInvUtil.java$
>>> >> >> $
>>>
>
> Appears to happen if, and ONLY if, the second line is blank (i.e. ^$ will match it as a regex)
>
>>>
>>>
>>> I update the FreBSD Vim port on the first of every month, but I'm
>>> happy to update early if there's a breakage.
>>>
>>> Updating is a matter of changing PORTVERSION in
>>> /usr/ports/editors/vim/Makefile, and running 'make makesum' from that
>>> dir.
>>
>>
>> Updated to 822 with no effect (see below)
>>
>>>
>>> Does this behavior change if you change TERM (say, screen-256color)?
>>
>>
>> No (with screen-256color)
>>
>>>
>>> If you ssh from the console? If you use a different terminal emulator?
>>
>>
>> If I use xterm (default settings and -rv) it disappears.

Interesting. And does that only happen for java files, or for other
files as well?

Could it be related to a plugin? Or do you have a listchars that
specifies a unicode character that isn't present in the font that
xfce4-term is using? You might try enabling plugins one at a time, not
setting listchars, and make sure that the file you're editing is using
UNIX line-endings.

It does on all files (for example here is a case of doing it on my vimrc)... the file in question was created from scratch in vim on FreeBSD 11.2 (version controlled by devel/aegis [which I am the maintainer of]):

set term=xterm-256color
  �
set t_Co=256
runtime colorscheme colors/slate.vim
syntax enable
:noh
:hi Constant ctermfg=220
:hi String ctermfg=220
:hi Identifier ctermfg=lightblue
:hi javaCommentTitle ctermfg=yellow
:hi javaDocComment ctermfg=178
:hi javaCommentTitle ctermfg=178
:hi javaAnnotation ctermfg=lightblue
:hi Comment ctermfg=178
:hi javaDocTags ctermfg=Yellow
:hi htmlTag ctermfg=220
:hi htmlEndTag ctermfg=220
:hi javaScriptBraces ctermfg=white
:hi javaScriptParens ctermfg=white
:hi javaScriptType ctermfg=white
:hi javaScriptFunction ctermfg=lightblue
:hi xmlTag ctermfg=lightblue
:hi xmlTagName ctermfg=lightblue
:set t_ti=^[[?1049h
:set t_te=

For completeness here is my uname -a:

FreeBSD timeless 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #1 r339445: Sat Oct 20 02:23:58 EDT 2018     root@timeless:/usr/obj/usr/src/sys/GENERIC  amd64

As far I know I am not using any plugins unless they came installed with the default port options here is my /var/db/ports/editors_vim/options:

# This file is auto-generated by 'make config'.
# Options for vim-8.1.0555
_OPTIONS_READ=vim-8.1.0555
_FILE_COMPLETE_OPTIONS_LIST=CSCOPE DEFAULT_VIMRC NLS XTERM_SAVE CTAGS_BASE CTAGS_EXUBERANT CTAGS_UNIVERSAL ATHENA CONSOLE GNOME GTK2 GTK3 MOTIF X11 LUA PERL PYTHON2 PYTHON3 RUBY SCHEME TCL
OPTIONS_FILE_SET+=CSCOPE
OPTIONS_FILE_SET+=DEFAULT_VIMRC
OPTIONS_FILE_SET+=NLS
OPTIONS_FILE_UNSET+=XTERM_SAVE
OPTIONS_FILE_UNSET+=CTAGS_BASE
OPTIONS_FILE_SET+=CTAGS_EXUBERANT
OPTIONS_FILE_UNSET+=CTAGS_UNIVERSAL
OPTIONS_FILE_UNSET+=ATHENA
OPTIONS_FILE_UNSET+=CONSOLE
OPTIONS_FILE_UNSET+=GNOME
OPTIONS_FILE_SET+=GTK2
OPTIONS_FILE_UNSET+=GTK3
OPTIONS_FILE_UNSET+=MOTIF
OPTIONS_FILE_UNSET+=X11
OPTIONS_FILE_UNSET+=LUA
OPTIONS_FILE_SET+=PERL
OPTIONS_FILE_SET+=PYTHON2
OPTIONS_FILE_UNSET+=PYTHON3
OPTIONS_FILE_SET+=RUBY
OPTIONS_FILE_UNSET+=SCHEME
OPTIONS_FILE_UNSET+=TCL

# Adam


--
Adam Weinberger
adamw@adamw.org // adamw@FreeBSD.org
https://www.adamw.org

--

Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

--
--
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 information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.