On Sat, Jan 26, 2019 at 9:54 AM Adam Weinberger <[email protected]> wrote:

> On Sat, Jan 26, 2019 at 1:59 AM Aryeh Friedman <[email protected]>
> 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 <
> [email protected]> wrote:
> >>
> >> On Sat, Jan 26, 2019 at 12:31 AM Aryeh Friedman
> >> <[email protected]> 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 <
> [email protected]> 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$
> >> >> $
> >> >>
> >> >> Platform info:
> >> >> OS: FreeBSD 11.2
> >> >> Terminal type: ssh (xterm-256color) via xfce4-term 0.8.7.4 on xfce4
> desktop (4.12)
> >> >> Vim --version output:
> >> >> VIM - Vi IMproved 8.1 (2018 May 18, compiled Jan 25 2019 04:31:10)
> >> >> Included patches: 1-676
> >> >> Compiled by aryehl@timeless
> >> >> Huge version with GTK2 GUI.  Features included (+) or not (-):
> >>
> >> This problem, or something quite like it, has recently been reported
> and fixed.
> >>
> >> The above is Vim 8.1.676. The latest source as of this writing is
> >> 8.1.822; IOW there has already been 146 patches since the version you
> >> used. Please try again with a newer Vim.
> >
> >
> > 1. Since FreeBSD uses a centralized port and the port is currently only
> up through 676 I will wait until the official maintainer updates the port
> >
> > 2. I do not see any patches with descriptions off hand in the patch
> inventory after 676 that appear to relate to this issue.
>
> 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.

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to