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

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

Stretch vim doesnt cut and paste

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

Contents

  Stretch vim doesnt cut and paste Rob van der Putten <rob@sput.nl> - 2017-08-19 14:00 +0200
    Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-19 14:10 +0200
      Re: Stretch vim doesnt cut and paste kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-08-20 13:30 +0200
        Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-20 18:30 +0200
          Re: Stretch vim doesnt cut and paste Nicolas George <george@nsup.org> - 2017-08-20 18:50 +0200
            Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-20 19:40 +0200
              Re: Stretch vim doesnt cut and paste Richard Hector <richard@walnut.gen.nz> - 2017-08-24 05:40 +0200
                Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-24 11:40 +0200
                  Re: Stretch vim doesnt cut and paste David Wright <deblis@lionunicorn.co.uk> - 2017-08-24 15:50 +0200
                    Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-24 17:20 +0200
                      Re: Stretch vim doesnt cut and paste Elimar Riesebieter <riesebie@lxtec.de> - 2017-08-24 22:10 +0200
                        Re: Stretch vim doesnt cut and paste Reco <recoverym4n@gmail.com> - 2017-08-24 22:50 +0200
        Re: Stretch vim doesnt cut and paste kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-08-21 01:10 +0200
    Re: Stretch vim doesnt cut and paste Nicolas George <george@nsup.org> - 2017-08-19 14:20 +0200
    Re: Stretch vim doesnt cut and paste Brian <ad44@cityscape.co.uk> - 2017-08-19 14:20 +0200
      Re: Stretch vim doesnt cut and paste Rob van der Putten <rob@sput.nl> - 2017-08-19 14:40 +0200
        Re: Stretch vim doesnt cut and paste behrad eslami <behrad_es@yahoo.com> - 2017-08-20 08:20 +0200

#185486 — Stretch vim doesnt cut and paste

Hi there


After a upgrade from jessie to stretch I can't use the mouse to cut and 
paste in vim.
nvi works, nano works.
As quick fix I removed xxd and installed the jessie version of vim, 
vim-common and vim-runtime. This does work.


Regards,
Rob

[toc] | [next] | [standalone]

#185488

	Hi.

On Sat, 19 Aug 2017 13:56:15 +0200
Rob van der Putten <rob@sput.nl> wrote:

> Hi there
> 
> 
> After a upgrade from jessie to stretch I can't use the mouse to cut and 
> paste in vim.
> nvi works, nano works.
> As quick fix I removed xxd and installed the jessie version of vim, 
> vim-common and vim-runtime. This does work.

A known problem. Apparently upstream thought (and Debian maintainer
followed) that it would be good idea to enable so-called 'mouse support'
in vim. As a result X cutbuffer ceased to function in vim.
They also enabled 'incremental search' by default too, which is
annoying to say the least.

It took me some time to figure a way to disable these 'innovations'
systemwide, but I got it:

echo let g:skip_defaults_vim = 1 >> /etc/vim/vimrc.local

Reco

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

#185557

On Sat, Aug 19, 2017 at 8:04 AM, Reco <recoverym4n@gmail.com> wrote:
>
> A known problem. Apparently upstream thought (and Debian maintainer
> followed) that it would be good idea to enable so-called 'mouse support'
> in vim. As a result X cutbuffer ceased to function in vim.
> They also enabled 'incremental search' by default too, which is
> annoying to say the least.
>
> It took me some time to figure a way to disable these 'innovations'
> systemwide, but I got it:
>
> echo let g:skip_defaults_vim = 1 >> /etc/vim/vimrc.local

Using a sledgehammer to crack a nut, uh? YMMV but I find that a lot of
those changes are good. If you are annoyed by the incremental search,
simply disable it by adding

set noic

in ~/.vimrc.

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

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

#185577

	Hi.

On Sun, 20 Aug 2017 07:22:34 -0400
kamaraju kusumanchi <raju.mailinglists@gmail.com> wrote:

> On Sat, Aug 19, 2017 at 8:04 AM, Reco <recoverym4n@gmail.com> wrote:
> >
> > A known problem. Apparently upstream thought (and Debian maintainer
> > followed) that it would be good idea to enable so-called 'mouse support'
> > in vim. As a result X cutbuffer ceased to function in vim.
> > They also enabled 'incremental search' by default too, which is
> > annoying to say the least.
> >
> > It took me some time to figure a way to disable these 'innovations'
> > systemwide, but I got it:
> >
> > echo let g:skip_defaults_vim = 1 >> /etc/vim/vimrc.local
> 
> Using a sledgehammer to crack a nut, uh? YMMV but I find that a lot of
> those changes are good. If you are annoyed by the incremental search,
> simply disable it by adding
> 
> set noic
> 
> in ~/.vimrc.

That part is simple (per-user). The hard question is - how can I force
vim to respect 'noic' without the need to create ~/.vimrc for every
single user that I use?

Modifying /etc/vim/vimrc as [1] suggests should work, but it'll be
annoying to deal with debconf on vim upgrades.

Reco

[1] http://layer-acht.org/thinking/blog/20170614-stretch-vim/

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

#185581

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

Le tridi 3 fructidor, an CCXXV, Reco a écrit :
> That part is simple (per-user). The hard question is - how can I force
> vim to respect 'noic' without the need to create ~/.vimrc for every
> single user that I use?

The same way you distribute any configuration change you make to any
software. If you have so many "users" that you use and not an
infrastructure to do that, then you have a bigger problem than noic.

But I must say, why anybody would want anything except
ignorecase+smartcase when it is possible as the default for an
interactive text editor is a mystery to me.

Regards,

-- 
  Nicolas George

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

#185585

On Sun, 20 Aug 2017 18:46:49 +0200
Nicolas George <george@nsup.org> wrote:

> Le tridi 3 fructidor, an CCXXV, Reco a écrit :
> > That part is simple (per-user). The hard question is - how can I force
> > vim to respect 'noic' without the need to create ~/.vimrc for every
> > single user that I use?
> 
> The same way you distribute any configuration change you make to any
> software. If you have so many "users" that you use and not an
> infrastructure to do that, then you have a bigger problem than noic.

I believe you're missing the point.
They invented configuration files in /etc to change behavior systemwide
(i.e. for all users at once). Putting any files into each users' homes
is a klugde. 

In jessie and before that one could put needed customizations
into /etc/vim/vimrc (and it works as of stretch)
or into /etc/vim/vimrc.local (and it's ignored in stretch).

But, as of stretch, g:skip_defaults_vim forces vim to
honor /etc/vim/vimrc.local, and that's the way it should behave for me.


> But I must say, why anybody would want anything except
> ignorecase+smartcase when it is possible as the default for an
> interactive text editor is a mystery to me.

They say that one should not argue about tastes. I prefer 'ic' for
instance.

And my original complaint was about 'incsearch', not 'ignorecase'. Some
mistake was made in this part of thread.

Reco

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

#185805

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

On 21/08/17 05:31, Reco wrote:
> In jessie and before that one could put needed customizations
> into /etc/vim/vimrc (and it works as of stretch)
> or into /etc/vim/vimrc.local (and it's ignored in stretch).

Looking at a stretch box (installed clean, not upgraded), /etc/vim/vimrc
has this at the bottom:

" Source a global configuration file if available
if filereadable("/etc/vim/vimrc.local")
  source /etc/vim/vimrc.local
endif

So it should be read. Is yours not readable by the user? (I don't have
one at all; I haven't felt the need yet)

Richard

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

#185814

	Hi.

On Thu, Aug 24, 2017 at 03:38:10PM +1200, Richard Hector wrote:
> On 21/08/17 05:31, Reco wrote:
> > In jessie and before that one could put needed customizations
> > into /etc/vim/vimrc (and it works as of stretch)
> > or into /etc/vim/vimrc.local (and it's ignored in stretch).
> 
> Looking at a stretch box (installed clean, not upgraded), /etc/vim/vimrc
> has this at the bottom:
> 
> " Source a global configuration file if available
> if filereadable("/etc/vim/vimrc.local")
>   source /etc/vim/vimrc.local
> endif
> 
> So it should be read. Is yours not readable by the user? (I don't have
> one at all; I haven't felt the need yet)

No, permissions for /etc/vim/vimrc.local are 644.
The problem is (had to use strace to figure this one out) that on vim
start /etc/vim/vimrc.local is read first, and
/usr/share/vim/vim80/defaults.vim after it.

Therefore any customizations put into /etc/vim/vimrc.local can be
overridden by defaults.vim, which is happpening for 'mouse' and
'incsearch' at least.

Unless you forbid vim to interpret defaults.vim at all.
It can be achieved by creating user's .vimrc, or 'g:skip_defaults_vim=1'.

Reco

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

#185828

On Thu 24 Aug 2017 at 12:37:45 (+0300), Reco wrote:
> 	Hi.
> 
> On Thu, Aug 24, 2017 at 03:38:10PM +1200, Richard Hector wrote:
> > On 21/08/17 05:31, Reco wrote:
> > > In jessie and before that one could put needed customizations
> > > into /etc/vim/vimrc (and it works as of stretch)
> > > or into /etc/vim/vimrc.local (and it's ignored in stretch).
> > 
> > Looking at a stretch box (installed clean, not upgraded), /etc/vim/vimrc
> > has this at the bottom:
> > 
> > " Source a global configuration file if available
> > if filereadable("/etc/vim/vimrc.local")
> >   source /etc/vim/vimrc.local
> > endif
> > 
> > So it should be read. Is yours not readable by the user? (I don't have
> > one at all; I haven't felt the need yet)
> 
> No, permissions for /etc/vim/vimrc.local are 644.
> The problem is (had to use strace to figure this one out) that on vim
> start /etc/vim/vimrc.local is read first, and
> /usr/share/vim/vim80/defaults.vim after it.
> 
> Therefore any customizations put into /etc/vim/vimrc.local can be
> overridden by defaults.vim, which is happpening for 'mouse' and
> 'incsearch' at least.
> 
> Unless you forbid vim to interpret defaults.vim at all.
> It can be achieved by creating user's .vimrc, or 'g:skip_defaults_vim=1'.

How does all this relate to   man vim   which appears to be
at least a decade old/out of date? I wasn't aware that the
last action of   man foo  ’s $MANOPT should be to append
any or all of /usr/share/doc/foo*/*README* to the manpage.

Cheers,
David.

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

#185833

	Hi.

On Thu, 24 Aug 2017 08:45:19 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:

> On Thu 24 Aug 2017 at 12:37:45 (+0300), Reco wrote:
> > 	Hi.
> > 
> > On Thu, Aug 24, 2017 at 03:38:10PM +1200, Richard Hector wrote:
> > > On 21/08/17 05:31, Reco wrote:
> > > > In jessie and before that one could put needed customizations
> > > > into /etc/vim/vimrc (and it works as of stretch)
> > > > or into /etc/vim/vimrc.local (and it's ignored in stretch).
> > > 
> > > Looking at a stretch box (installed clean, not upgraded), /etc/vim/vimrc
> > > has this at the bottom:
> > > 
> > > " Source a global configuration file if available
> > > if filereadable("/etc/vim/vimrc.local")
> > >   source /etc/vim/vimrc.local
> > > endif
> > > 
> > > So it should be read. Is yours not readable by the user? (I don't have
> > > one at all; I haven't felt the need yet)
> > 
> > No, permissions for /etc/vim/vimrc.local are 644.
> > The problem is (had to use strace to figure this one out) that on vim
> > start /etc/vim/vimrc.local is read first, and
> > /usr/share/vim/vim80/defaults.vim after it.
> > 
> > Therefore any customizations put into /etc/vim/vimrc.local can be
> > overridden by defaults.vim, which is happpening for 'mouse' and
> > 'incsearch' at least.
> > 
> > Unless you forbid vim to interpret defaults.vim at all.
> > It can be achieved by creating user's .vimrc, or 'g:skip_defaults_vim=1'.
> 
> How does all this relate to   man vim   which appears to be
> at least a decade old/out of date? 

vim(1) does not mention defaults.vim, so it must be a case of obsolete
documentation.
That, and I'm too lazy to view vim source.

Reco

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

#185858

* Reco <recoverym4n@gmail.com> [2017-08-24 18:16 +0300]:

[...]
> vim(1) does not mention defaults.vim, so it must be a case of obsolete
> documentation.
> That, and I'm too lazy to view vim source.

Read file:///usr/share/doc/vim-common/NEWS.Debian.gz

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

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

#185864

	Hi.

On Thu, 24 Aug 2017 21:59:36 +0200
Elimar Riesebieter <riesebie@lxtec.de> wrote:

> * Reco <recoverym4n@gmail.com> [2017-08-24 18:16 +0300]:
> 
> [...]
> > vim(1) does not mention defaults.vim, so it must be a case of obsolete
> > documentation.
> > That, and I'm too lazy to view vim source.
> 
> Read file:///usr/share/doc/vim-common/NEWS.Debian.gz

Thanks. That reminds me to reinstall apt-listchanges which I should've
done *before* upgrading to stretch.

Reco

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

#185606

On Sun, Aug 20, 2017 at 7:22 AM, kamaraju kusumanchi
<raju.mailinglists@gmail.com> wrote:
>
> Using a sledgehammer to crack a nut, uh? YMMV but I find that a lot of
> those changes are good. If you are annoyed by the incremental search,
> simply disable it by adding
>
> set noic
>
> in ~/.vimrc.
>
Sorry, I meant "set nois" as in noincsearch.

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

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

#185489

Le duodi 2 fructidor, an CCXXV, Rob van der Putten a écrit :
> After a upgrade from jessie to stretch I can't use the mouse to cut and
> paste in vim.

Try "set mouse=" (empty option).

Regards,

-- 
  Nicolas George

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

#185490

On Sat 19 Aug 2017 at 13:56:15 +0200, Rob van der Putten wrote:

> After a upgrade from jessie to stretch I can't use the mouse to cut and
> paste in vim.
> nvi works, nano works.
> As quick fix I removed xxd and installed the jessie version of vim,
> vim-common and vim-runtime. This does work.

"set mouse=" in ~/.vimrc.

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

#185491

Hi there


On 19/08/17 14:10, Brian wrote:

> "set mouse=" in ~/.vimrc.

In /etc/vim/vimrc it doesn't work.
In ~/.vimrc it does.

Thanks!


Regards,
Rob

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

#185547

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

Press shift and select lines that you want to copy

On Saturday, August 19, 2017, 5:06:33 PM GMT+4:30, Rob van der Putten <rob@sput.nl> wrote:

Hi there


On 19/08/17 14:10, Brian wrote:

> "set mouse=" in ~/.vimrc.

In /etc/vim/vimrc it doesn't work.
In ~/.vimrc it does.

Thanks!


Regards,
Rob

[toc] | [prev] | [standalone]

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

csiph-web