Re: recent change to vim defaults?

[Julian Elischer]

On 19/01/2017 11:18 AM, Julian Elischer wrote:

On 19/01/2017 1:37 AM, Adam Weinberger wrote:
On 18 Jan, 2017, at 10:35, Julian Elischer  
wrote:


On 17/01/2017 1:23 AM, Adam Weinberger wrote:
On 16 Jan, 2017, at 9:25, Baptiste Daroussin  
wrote:


On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
I noticed that suddenly vim is grabbing mouse movements, which 
makes life

really hard.

Was there a specific revision that brought in this change, and 
can it be

removed?
This change appeared in one of the last patchset of vim 7.4 and 
was one of the

"features" of the vim 8.0 release.

I do agree this is just totally painful :(

Best regards,
Bapt
One of the things that I inherited with the Vim port was the 
DEFAULT_VIMRC option (which installs 
/usr/ports/editors/vim/files/vimrc), and I haven't touched it.


I have moused disabled in all my boxes so I have no idea about 
bad mouse behaviour in Vim. If there is a bad default that is 
causing grief, let's just fix it in that default vimrc.


I'm not really understanding what the unexpected behaviour is so 
I can't make an intelligent recommendation myself, but I'll go 
with whatever you folks suggest.


# Adam

I'm in iterm on my mac.
I ssh to a freebsd machine
I use vim on a file.
I used to be able to use the mouse on my mac to copy a few lines 
into the cut buffer.. slide-shift-click etc..
now suddenly if I try highlight some code in vim to copy it vim 
drags stuff around, scrolls up and down, deletes stuff and 
generally makes a mess.

if click, instead of starting a copy zone it grabs some of the text.

basically it makes hte mouse useless.
I can;t copy and paste from a file I'm ediitng. I end up having to 
exit vim and do it in vi.
There have been a number of recommendations in this thread for you, 
Julian, including "set mouse=a" and "set mouse=v". Test some of 
them out and let me know what works for you.


actually I never saw one about mouse=a however I did see and try 
mouse=v which didn't work for me.


I have now tried mouse=a and am happy to say that that does what I 
need.

thanks!


actually no, 'set mouse='
seems to be what I want.. not sure why I thought =a worked:




# Adam




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Julian Elischer]

On 19/01/2017 1:37 AM, Adam Weinberger wrote:

On 18 Jan, 2017, at 10:35, Julian Elischer  wrote:

On 17/01/2017 1:23 AM, Adam Weinberger wrote:

On 16 Jan, 2017, at 9:25, Baptiste Daroussin  wrote:

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:

I noticed that suddenly vim is grabbing mouse movements, which makes life
really hard.

Was there a specific revision that brought in this change, and can it be
removed?

This change appeared in one of the last patchset of vim 7.4 and was one of the
"features" of the vim 8.0 release.

I do agree this is just totally painful :(

Best regards,
Bapt

One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
touched it.

I have moused disabled in all my boxes so I have no idea about bad mouse 
behaviour in Vim. If there is a bad default that is causing grief, let's just 
fix it in that default vimrc.

I'm not really understanding what the unexpected behaviour is so I can't make 
an intelligent recommendation myself, but I'll go with whatever you folks 
suggest.

# Adam

I'm in iterm on my mac.
I ssh to a freebsd machine
I use vim on a file.
I used to be able to use the mouse on my mac to copy a few lines into the cut 
buffer.. slide-shift-click etc..
now suddenly if I try highlight some code in vim to copy it vim drags stuff 
around, scrolls up and down, deletes stuff and generally makes a mess.
if click, instead of starting a copy zone it grabs some of the text.

basically it makes hte mouse useless.
I can;t copy and paste from a file I'm ediitng. I end up having to exit vim and 
do it in vi.

There have been a number of recommendations in this thread for you, Julian, including "set 
mouse=a" and "set mouse=v". Test some of them out and let me know what works for you.


actually I never saw one about mouse=a however I did see and try 
mouse=v which didn't work for me.


I have now tried mouse=a and am happy to say that that does what I need.
thanks!



# Adam




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Pete Wright]

On 1/18/17 10:24 AM, Alexander Kabaev wrote:

On Wed, 18 Jan 2017 10:06:55 -0800
Pete Wright  wrote:


On 1/18/17 10:01 AM, Julian Elischer wrote:

On 18/01/2017 5:03 PM, Raimund Sacherer wrote:

I have to put mouse=v to get the behavior I am used to.

Best


doesn't really work for me.

vim is still taking mouse events



kinda feel like it we need a "classic" vim port that is from the v7.x
codebase since i suspect the changes to mouse behaviour in v8.x is
only the beginning of lots of suspect changes to the vim codebase :/

i went through the code for vim the other day and couldn't figure out
a way to disable entering visual-mode via mouseclick as a compile
time option.  perhaps we should preserve the expected behaviour by
updating /usr/local/etc/vim/vimrc?




I just applied this diff against my global vimrc file and it now 
disables the visual mode by default function:


$ diff -u vimrc.sample vimrc
--- vimrc.sample2017-01-13 22:39:36.0 -0800
+++ vimrc   2017-01-18 10:51:48.020039000 -0800
@@ -3,10 +3,10 @@
 endif

 let g:is_posix = 1
-set nocompatible
 set bs=indent,eol,start
 set history=50
 set ruler
+set mouse-=a

 if _Co > 2 || has("gui_running")
syntax on



I'm not %100 clear why it was setting "nocompatible" - but once I 
removed it it disabled visual-mode-on-mouse-click.  I'll be managing 
this on my systems via our cfg mgmt systems but it'd be super if this, 
or something similar, was the default.


-pete

--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Alexander Kabaev]

On Wed, 18 Jan 2017 10:06:55 -0800
Pete Wright  wrote:

> On 1/18/17 10:01 AM, Julian Elischer wrote:
> > On 18/01/2017 5:03 PM, Raimund Sacherer wrote:  
> >> I have to put mouse=v to get the behavior I am used to.
> >>
> >> Best  
> >
> > doesn't really work for me.
> >
> > vim is still taking mouse events
> >  
> 
> kinda feel like it we need a "classic" vim port that is from the v7.x 
> codebase since i suspect the changes to mouse behaviour in v8.x is
> only the beginning of lots of suspect changes to the vim codebase :/
> 
> i went through the code for vim the other day and couldn't figure out
> a way to disable entering visual-mode via mouseclick as a compile
> time option.  perhaps we should preserve the expected behaviour by
> updating /usr/local/etc/vim/vimrc?
> 
> -p
> 
> 
> -- 
> Pete Wright
> p...@nomadlogic.org
> nomadlogicLA

What we need, IMHO, of course, is to stop jamming _example_ config file
down everyone's throat. Not even Linux does install that file unchanged.

-- 
Alexander Kabaev


pgpHx_puTsrm7.pgp
Description: Цифровая подпись OpenPGP

Re: recent change to vim defaults?

[Pete Wright]

On 1/18/17 10:01 AM, Julian Elischer wrote:

On 18/01/2017 5:03 PM, Raimund Sacherer wrote:

I have to put mouse=v to get the behavior I am used to.

Best


doesn't really work for me.

vim is still taking mouse events



kinda feel like it we need a "classic" vim port that is from the v7.x 
codebase since i suspect the changes to mouse behaviour in v8.x is only 
the beginning of lots of suspect changes to the vim codebase :/


i went through the code for vim the other day and couldn't figure out a 
way to disable entering visual-mode via mouseclick as a compile time 
option.  perhaps we should preserve the expected behaviour by updating 
/usr/local/etc/vim/vimrc?


-p


--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 18 Jan, 2017, at 10:35, Julian Elischer  wrote:
> 
> On 17/01/2017 1:23 AM, Adam Weinberger wrote:
>>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin  wrote:
>>> 
>>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
 I noticed that suddenly vim is grabbing mouse movements, which makes life
 really hard.
 
 Was there a specific revision that brought in this change, and can it be
 removed?
>>> This change appeared in one of the last patchset of vim 7.4 and was one of 
>>> the
>>> "features" of the vim 8.0 release.
>>> 
>>> I do agree this is just totally painful :(
>>> 
>>> Best regards,
>>> Bapt
>> One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
>> option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
>> touched it.
>> 
>> I have moused disabled in all my boxes so I have no idea about bad mouse 
>> behaviour in Vim. If there is a bad default that is causing grief, let's 
>> just fix it in that default vimrc.
>> 
>> I'm not really understanding what the unexpected behaviour is so I can't 
>> make an intelligent recommendation myself, but I'll go with whatever you 
>> folks suggest.
>> 
>> # Adam
> I'm in iterm on my mac.
> I ssh to a freebsd machine
> I use vim on a file.
> I used to be able to use the mouse on my mac to copy a few lines into the cut 
> buffer.. slide-shift-click etc..
> now suddenly if I try highlight some code in vim to copy it vim drags stuff 
> around, scrolls up and down, deletes stuff and generally makes a mess.
> if click, instead of starting a copy zone it grabs some of the text.
> 
> basically it makes hte mouse useless.
> I can;t copy and paste from a file I'm ediitng. I end up having to exit vim 
> and do it in vi.

There have been a number of recommendations in this thread for you, Julian, 
including "set mouse=a" and "set mouse=v". Test some of them out and let me 
know what works for you.

# Adam


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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Julian Elischer]

On 18/01/2017 5:03 PM, Raimund Sacherer wrote:

I have to put mouse=v to get the behavior I am used to.

Best


doesn't really work for me.

vim is still taking mouse events


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Baptiste Daroussin]

On Wed, Jan 18, 2017 at 10:37:32AM -0700, Adam Weinberger wrote:
> > On 18 Jan, 2017, at 10:35, Julian Elischer  wrote:
> > 
> > On 17/01/2017 1:23 AM, Adam Weinberger wrote:
> >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin  wrote:
> >>> 
> >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
>  I noticed that suddenly vim is grabbing mouse movements, which makes life
>  really hard.
>  
>  Was there a specific revision that brought in this change, and can it be
>  removed?
> >>> This change appeared in one of the last patchset of vim 7.4 and was one 
> >>> of the
> >>> "features" of the vim 8.0 release.
> >>> 
> >>> I do agree this is just totally painful :(
> >>> 
> >>> Best regards,
> >>> Bapt
> >> One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
> >> option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
> >> touched it.
> >> 
> >> I have moused disabled in all my boxes so I have no idea about bad mouse 
> >> behaviour in Vim. If there is a bad default that is causing grief, let's 
> >> just fix it in that default vimrc.
> >> 
> >> I'm not really understanding what the unexpected behaviour is so I can't 
> >> make an intelligent recommendation myself, but I'll go with whatever you 
> >> folks suggest.
> >> 
> >> # Adam
> > I'm in iterm on my mac.
> > I ssh to a freebsd machine
> > I use vim on a file.
> > I used to be able to use the mouse on my mac to copy a few lines into the 
> > cut buffer.. slide-shift-click etc..
> > now suddenly if I try highlight some code in vim to copy it vim drags stuff 
> > around, scrolls up and down, deletes stuff and generally makes a mess.
> > if click, instead of starting a copy zone it grabs some of the text.
> > 
> > basically it makes hte mouse useless.
> > I can;t copy and paste from a file I'm ediitng. I end up having to exit vim 
> > and do it in vi.
> 
> There have been a number of recommendations in this thread for you, Julian, 
> including "set mouse=a" and "set mouse=v". Test some of them out and let me 
> know what works for you.

set mouse=
(with nothing) brings back the original behaviour

Bapt


signature.asc
Description: PGP signature

Re: recent change to vim defaults?

[Julian Elischer]

On 17/01/2017 1:23 AM, Adam Weinberger wrote:

On 16 Jan, 2017, at 9:25, Baptiste Daroussin  wrote:

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:

I noticed that suddenly vim is grabbing mouse movements, which makes life
really hard.

Was there a specific revision that brought in this change, and can it be
removed?

This change appeared in one of the last patchset of vim 7.4 and was one of the
"features" of the vim 8.0 release.

I do agree this is just totally painful :(

Best regards,
Bapt

One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
touched it.

I have moused disabled in all my boxes so I have no idea about bad mouse 
behaviour in Vim. If there is a bad default that is causing grief, let's just 
fix it in that default vimrc.

I'm not really understanding what the unexpected behaviour is so I can't make 
an intelligent recommendation myself, but I'll go with whatever you folks 
suggest.

# Adam

I'm in iterm on my mac.
I ssh to a freebsd machine
I use vim on a file.
I used to be able to use the mouse on my mac to copy a few lines into 
the cut buffer..  slide-shift-click etc..
now suddenly if I try highlight some code in vim to copy it vim drags 
stuff around, scrolls up and down, deletes stuff and generally makes a 
mess.

if click, instead of starting a copy zone it grabs some of the text.

basically it makes hte mouse useless.
I can;t copy and paste from a file I'm ediitng. I end up having to 
exit vim and do it in vi.







___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Raimund Sacherer]

I have to put mouse=v to get the behavior I am used to.

Best⁣

Sent from TypeApp ​

On Jan 18, 2017, 08:46, at 08:46, Julian Elischer  wrote:
>On 17/01/2017 12:07 AM, ohauer wrote:
>> I suspect you mean the /usr/local/etc/vim/vimrc and gvimrc files.
>> That was the first place I've tried to overwrite it, but without 
>> luck (even with set mouse=) but it works in ~/.vimrc
>
>what to put IN the file?
>>
>> -- 
>> olli
>> -- 
>> send with broken GMX mailer client, sorry for tofu and html scrap
>> On 15/01/2017, 22:48 Benjamin Kaduk  wrote:
>>
>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
>> > I noticed that suddenly vim is grabbing mouse movements, which
>> makes
>> > life really hard.
>> >
>> > Was there a specific revision that brought in this change, and
>> can it
>> > be removed?
>>
>> I remember seeing something go by during an upgrade somewhat
>> recently
>> about there now being a defaults file that gets used when a user
>> does
>> not specify a .vimrc. Unfortunately, I don't remember whether I
>saw
>> that notice on a FreeBSD machine or a Debian one, and haven't
>> been able
>> to find the notice I remember through searching some likely
>places.
>>
>> Just to check: do you have a .vimrc file in place already?
>>
>not yet.
>when I work out what to put into it I will make it.
>
>>
>> -Ben
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
>> "freebsd-current-unsubscr...@freebsd.org"
>>
>
>___
>freebsd-po...@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
>"freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Julian Elischer]

On 17/01/2017 12:07 AM, ohauer wrote:

I suspect you mean the /usr/local/etc/vim/vimrc and gvimrc files.
That was the first place I've tried to overwrite it, but without 
luck (even with set mouse=) but it works in ~/.vimrc


what to put IN the file?


--
olli
--
send with broken GMX mailer client, sorry for tofu and html scrap
On 15/01/2017, 22:48 Benjamin Kaduk  wrote:

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> I noticed that suddenly vim is grabbing mouse movements, which
makes
> life really hard.
>
> Was there a specific revision that brought in this change, and
can it
> be removed?

I remember seeing something go by during an upgrade somewhat
recently
about there now being a defaults file that gets used when a user
does
not specify a .vimrc. Unfortunately, I don't remember whether I saw
that notice on a FreeBSD machine or a Debian one, and haven't
been able
to find the notice I remember through searching some likely places.

Just to check: do you have a .vimrc file in place already?


not yet.
when I work out what to put into it I will make it.



-Ben
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 16 Jan, 2017, at 9:25, Baptiste Daroussin  wrote:
> 
> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
>> I noticed that suddenly vim is grabbing mouse movements, which makes life
>> really hard.
>> 
>> Was there a specific revision that brought in this change, and can it be
>> removed?
> 
> This change appeared in one of the last patchset of vim 7.4 and was one of the
> "features" of the vim 8.0 release.
> 
> I do agree this is just totally painful :(
> 
> Best regards,
> Bapt

One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
touched it.

I have moused disabled in all my boxes so I have no idea about bad mouse 
behaviour in Vim. If there is a bad default that is causing grief, let's just 
fix it in that default vimrc.

I'm not really understanding what the unexpected behaviour is so I can't make 
an intelligent recommendation myself, but I'll go with whatever you folks 
suggest.

# Adam


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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Baptiste Daroussin]

On Mon, Jan 16, 2017 at 07:46:41PM +0300, Slawa Olhovchenkov wrote:
> On Mon, Jan 16, 2017 at 05:25:26PM +0100, Baptiste Daroussin wrote:
> 
> > On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> > > I noticed that suddenly vim is grabbing mouse movements, which makes life
> > > really hard.
> > > 
> > > Was there a specific revision that brought in this change, and can it be
> > > removed?
> > 
> > This change appeared in one of the last patchset of vim 7.4 and was one of 
> > the
> > "features" of the vim 8.0 release.
> > 
> > I do agree this is just totally painful :(
> 
> Wat about edit 8-bit files in utf-8 locale?
> Still corrupted files?

What are you speaking about I never had this issue with vim

We had this issue with vi in base which is now worked arounded so it just fails
so save instead of corrupting (which is still bad but a bit better :))

Bapt


signature.asc
Description: PGP signature

Re: recent change to vim defaults?

[Slawa Olhovchenkov]

On Mon, Jan 16, 2017 at 05:25:26PM +0100, Baptiste Daroussin wrote:

> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> > I noticed that suddenly vim is grabbing mouse movements, which makes life
> > really hard.
> > 
> > Was there a specific revision that brought in this change, and can it be
> > removed?
> 
> This change appeared in one of the last patchset of vim 7.4 and was one of the
> "features" of the vim 8.0 release.
> 
> I do agree this is just totally painful :(

Wat about edit 8-bit files in utf-8 locale?
Still corrupted files?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Baptiste Daroussin]

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> I noticed that suddenly vim is grabbing mouse movements, which makes life
> really hard.
> 
> Was there a specific revision that brought in this change, and can it be
> removed?

This change appeared in one of the last patchset of vim 7.4 and was one of the
"features" of the vim 8.0 release.

I do agree this is just totally painful :(

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: Re: recent change to vim defaults?

[ohauer]

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Benjamin Kaduk]

On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
> I noticed that suddenly vim is grabbing mouse movements, which makes 
> life really hard.
> 
> Was there a specific revision that brought in this change, and can it 
> be removed?

I remember seeing something go by during an upgrade somewhat recently
about there now being a defaults file that gets used when a user does
not specify a .vimrc.  Unfortunately, I don't remember whether I saw
that notice on a FreeBSD machine or a Debian one, and haven't been able
to find the notice I remember through searching some likely places.

Just to check: do you have a .vimrc file in place already?

-Ben
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Ngie Cooper]

> On Jan 15, 2017, at 08:03, Julian Elischer  wrote:
> 
> I noticed that suddenly vim is grabbing mouse movements, which makes life 
> really hard.
> 
> Was there a specific revision that brought in this change, and can it be 
> removed?

"set mouse=" will disable the feature you're describing.
-Ngie

PS I find the new feature incredibly annoying and disable it on all FreeBSD 
clients where I install vim.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Steven Hartland]

On 15/01/2017 17:45, Pete Wright wrote:



On 1/15/17 8:22 AM, Kyle Evans wrote:

On Jan 15, 2017 10:03, "Julian Elischer"  wrote:

I noticed that suddenly vim is grabbing mouse movements, which makes 
life

really hard.

Was there a specific revision that brought in this change, and can it be
removed?




Yea I can second this - IIRC it looks like around Sept or Oct vim now 
defaults to enabling Visual Mode.  I've been setting this in my 
~/.vimrc to disable it - but not enabling Visual Mode by default would 
awesome for me:


set mouse-=a

Yer we hatted this change too.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Pete Wright]

On 1/15/17 8:22 AM, Kyle Evans wrote:

On Jan 15, 2017 10:03, "Julian Elischer"  wrote:

I noticed that suddenly vim is grabbing mouse movements, which makes life
really hard.

Was there a specific revision that brought in this change, and can it be
removed?




Yea I can second this - IIRC it looks like around Sept or Oct vim now 
defaults to enabling Visual Mode.  I've been setting this in my ~/.vimrc 
to disable it - but not enabling Visual Mode by default would awesome 
for me:


set mouse-=a


-pete

--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 15 Jan, 2017, at 9:03, Julian Elischer  wrote:
> 
> I noticed that suddenly vim is grabbing mouse movements, which makes life 
> really hard.
> 
> Was there a specific revision that brought in this change, and can it be 
> removed?

Which patchlevel are you running?

# Adam


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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: recent change to vim defaults?

[Kyle Evans]

On Jan 15, 2017 10:03, "Julian Elischer"  wrote:

I noticed that suddenly vim is grabbing mouse movements, which makes life
really hard.

Was there a specific revision that brought in this change, and can it be
removed?

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Hi,

You might add "set mouse=v" to your vimrc -- it was a new default as of
8.0, IIRC. "set nohl" if the new highlighted of search matches irritates as
well.

Thanks,

Kyle Evans
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"