Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #210997 > unrolled thread

buster changes vim mouse behavior again...

Back to article view | Back to linux.debian.user

Contents

  buster changes vim mouse behavior again... Dave Sherohman <dave@sherohman.org> - 2019-07-08 15:50 +0200
    Re: buster changes vim mouse behavior again... Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 20:00 +0200
      Re: buster changes vim mouse behavior again... Dave Sherohman <dave@sherohman.org> - 2019-07-09 09:30 +0200
        Re: buster changes vim mouse behavior again... Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 07:00 +0200

#210997 — buster changes vim mouse behavior again...

Last time around, stretch changed mouse behavior in vim by setting
"mouse=a" by default.  To deal with this, my checklist for stretch
updates/installs includes

---
vi /etc/vim/vimrc.local
:set mouse=
:set paste
O
" Don't silently ignore these settings in favor of those in default.vim
let g:skip_defaults_vim = 1

" Middle-mouse should paste from X clipboard, NOT vim clipboard!
set mouse=
---

I copy (mouse highlight)/paste (middle-click) the first line into my
terminal, manually type the first `:set mouse=`, and then copy/paste the
rest of it.

Works great in stretch.

Today I did a test install of buster, however, and found a new problem:
It seems that buster's vim detects the middle-click and "helpfully" goes
immediately into insert mode, meaning that ":set paste" and "O" are
entered as part of the file contents rather than being processed as
commands.

I suppose that's handy for simple cases like this, where I ultimately am
just inserting text into a file, but I also frequently want to run the
same command in vim on a couple dozen different files, so it's really
handy to be able to paste commands into the vim window and have the
command executed instead of being inserted into the file's content.

So how do I bring back the old behavior?

In addition to ":set mouse=", I've also tried ":set ttymouse=" and
":set sessionoptions-=terminal", but these had no effect on this
behavior.



Crossposting notice:  I have also posted this question on the vi/vim
stack exchange site at
https://vi.stackexchange.com/questions/20548/allow-pasting-into-all-modes-not-just-insert

-- 
Dave Sherohman

[toc] | [next] | [standalone]

#211019

[Multipart message — attachments visible in raw view] — view raw

On Lu, 08 iul 19, 08:48:15, Dave Sherohman wrote:
> 
> Today I did a test install of buster, however, and found a new problem:
> It seems that buster's vim detects the middle-click and "helpfully" goes
> immediately into insert mode, meaning that ":set paste" and "O" are
> entered as part of the file contents rather than being processed as
> commands.

So far I haven't been able to make middle click reliably[1] paste into 
vim, but I attributed that to my unusual setup:

1. ssh from Chrome OS to a buster running screen.
2. Debian buster with LXDE on Crouton (basically a chroot under Chrome 
OS)

Same with neovim.

If you do figure out how it's supposed to work please do post on list.

[1] on rare occasions it does work, once. So far I was not able to find 
the pattern.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#211064

On Mon, Jul 08, 2019 at 08:50:56PM +0300, Andrei POPESCU wrote:
> On Lu, 08 iul 19, 08:48:15, Dave Sherohman wrote:
> > Today I did a test install of buster, however, and found a new problem:
> > It seems that buster's vim detects the middle-click and "helpfully" goes
> > immediately into insert mode, meaning that ":set paste" and "O" are
> > entered as part of the file contents rather than being processed as
> > commands.

> If you do figure out how it's supposed to work please do post on list.

My stackexchange question was identified as a duplicate of
https://vi.stackexchange.com/questions/18001/why-cant-i-paste-commands-into-vi
which gave me enough information to track down ":set t_BE=" (in addition
to the existing ":set mouse=") as a solution to my problem.

A full description of the behavior can be found at
https://vimhelp.org/term.txt.html if you do a search in the page for
"xterm-bracketed-paste".

":set termcap" shows that stretch's vim doesn't support the t_BE
setting, which is why it doesn't need to be cleared there.

-- 
Dave Sherohman

[toc] | [prev] | [next] | [standalone]

#211130

[Multipart message — attachments visible in raw view] — view raw

On Ma, 09 iul 19, 02:20:53, Dave Sherohman wrote:
> On Mon, Jul 08, 2019 at 08:50:56PM +0300, Andrei POPESCU wrote:
> 
> > If you do figure out how it's supposed to work please do post on list.
> 
> My stackexchange question was identified as a duplicate of
> https://vi.stackexchange.com/questions/18001/why-cant-i-paste-commands-into-vi
> which gave me enough information to track down ":set t_BE=" (in addition
> to the existing ":set mouse=") as a solution to my problem.
> 
> A full description of the behavior can be found at
> https://vimhelp.org/term.txt.html if you do a search in the page for
> "xterm-bracketed-paste".
> 
> ":set termcap" shows that stretch's vim doesn't support the t_BE
> setting, which is why it doesn't need to be cleared there.

This did result in some progress.

I will need to investigate/experiment more as well as do a proper review 
of my .vimrc (untouched for quite some time).

Many thanks,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web