Re: Vim selection underlined rather than reversed

On Monday, April 15, 2019 at 8:15:19 PM UTC+1, Christian Brabandt wrote:
> On Mo, 15 Apr 2019, Jeenu wrote:
>
> > On Monday, April 15, 2019 at 7:18:03 PM UTC+1, Tony Mechelynck wrote:
> > > On Mon, Apr 15, 2019 at 5:24 PM Jeenu wrote:
> > > >
> > > > Sometimes, after I attach to a tmux session, visual selection in an already-running vim instance is shown as underlined instead of reversed. See the attached files for the difference; both are from the same host - one from new, and the other from existing session. The only way out I've found is to quit and launch vim again. Does any one know why this happens and/or how to fix it?
> > > >
> > > > This is the same problem as someone had posted a while ago: https://superuser.com/questions/1186500/vim-visually-selected-text-sometimes-appears-as-underlined-not-reversed
> > > >
> > > > Thanks,
> > > > Jeenu
> > >
> > > I don't know why it happens but I know how to find out: next time the
> > > problem happens, and after making sure Vim is in Normal mode (this
> > > will usually mean hitting <Esc>, which will clear the Visual
> > > highlighting) type
> > >
> > > :verbose hi Visual
> >
> > I've attached screen shots capture of running the command two sessions. The output of the hi command shows reversed mode in both sessions.
> >
> > Also, both sessions say background is dark.
> >
> > Not sure what to make of these.
>
> Please show the text output.

:verbose hi Visual
Visual xxx term=reverse cterm=reverse ctermbg=242 guifg=khaki guibg=olivedrab
Last set from /usr/share/vim/vim74/colors/desert.vim
Press ENTER or type command to continue

> Another thing that is likely to be the cause is, Vim is using the
> VisualNOS highlighting group. This is used, when Vim cannot connect to
> the X Server. You mentioned using tmux and re-attaching sessions, so my
> guess is, the re-attachment made Vim not correctly reset the X connect.
>
> So the different highlighting is a way to let you know of it.
>
> There was an issue about Vim not correctly resetting up the X
> connection, (I believe #3649) and a fix seems to have been included by
> 8.1.0615.

The Cygwin server I'm running on my Windows host (vim runs on a remote Linux host) did restart, so could be that issue.

Jeenu

--
--
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.