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

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

Copy from Firefox and paste into Terminal with Vim

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

Contents

  Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-06 00:20 +0100
    Re: Copy from Firefox and paste into Terminal with Vim Bret Busby <bret@busby.net> - 2024-02-06 00:50 +0100
      Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-06 01:30 +0100
    Re: Copy from Firefox and paste into Terminal with Vim Dan Ritter <dsr@randomstring.org> - 2024-02-06 02:10 +0100
      Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-06 08:10 +0100
        Re: Copy from Firefox and paste into Terminal with Vim Dan Ritter <dsr@randomstring.org> - 2024-02-06 12:40 +0100
          Re: Copy from Firefox and paste into Terminal with Vim Greg Wooledge <greg@wooledge.org> - 2024-02-06 13:50 +0100
          Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 08:10 +0100
            Re: Copy from Firefox and paste into Terminal with Vim Greg Wooledge <greg@wooledge.org> - 2024-02-07 13:30 +0100
              Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-07 13:50 +0100
    Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-06 04:10 +0100
      Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-06 07:30 +0100
        Re: Copy from Firefox and paste into Terminal with Vim Greg Wooledge <greg@wooledge.org> - 2024-02-06 13:30 +0100
          Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-06 15:40 +0100
            Re: Copy from Firefox and paste into Terminal with Vim Greg Wooledge <greg@wooledge.org> - 2024-02-06 16:00 +0100
              Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-06 18:10 +0100
                Re: Copy from Firefox and paste into Terminal with Vim Nicolas George <george@nsup.org> - 2024-02-06 18:40 +0100
                  xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from Firefox and  paste into Terminal with Vim] Max Nikulin <manikulin@gmail.com> - 2024-02-07 04:30 +0100
                    Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from  Firefox and paste into Terminal with Vim] Nicolas George <george@nsup.org> - 2024-02-07 13:30 +0100
                      Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from Firefox and paste into Terminal with Vim] Stefan Monnier <monnier@iro.umontreal.ca> - 2024-02-07 14:20 +0100
                        Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from  Firefox and paste into Terminal with Vim] debian-user@howorth.org.uk - 2024-02-07 21:20 +0100
                      Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from Firefox  and paste into Terminal with Vim] Max Nikulin <manikulin@gmail.com> - 2024-02-07 18:10 +0100
                      C-Ins vs. C-c [was: xterm PRIMARY and CLIPBOARD selection] Firefox  and paste into Terminal with Vim] <tomas@tuxteam.de> - 2024-02-07 19:50 +0100
          Re: Copy from Firefox and paste into Terminal with Vim debian-user@howorth.org.uk - 2024-02-06 16:40 +0100
            Re: Copy from Firefox and paste into Terminal with Vim Greg Wooledge <greg@wooledge.org> - 2024-02-06 17:10 +0100
          Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 08:30 +0100
        Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-06 15:30 +0100
          Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 09:30 +0100
    Re: Copy from Firefox and paste into Terminal with Vim <tomas@tuxteam.de> - 2024-02-06 06:50 +0100
      Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-06 08:10 +0100
        Re: Copy from Firefox and paste into Terminal with Vim <tomas@tuxteam.de> - 2024-02-06 09:00 +0100
        Re: Copy from Firefox and paste into Terminal with Vim Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-02-06 09:20 +0100
          Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 08:30 +0100
      Re: Copy from Firefox and paste into Terminal with Vim John Hasler <john@sugarbit.com> - 2024-02-06 14:50 +0100
        Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 08:50 +0100
    Re: Copy from Firefox and paste into Terminal with Vim Ralph Aichinger <ra@h5.or.at> - 2024-02-06 13:00 +0100
      Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-06 15:40 +0100
        Re: Copy from Firefox and paste into Terminal with Vim <tomas@tuxteam.de> - 2024-02-06 15:40 +0100
        Re: Copy from Firefox and paste into Terminal with Vim Ralph Aichinger <ra@h5.or.at> - 2024-02-06 19:00 +0100
          Re: Copy from Firefox and paste into Terminal with Vim Max Nikulin <manikulin@gmail.com> - 2024-02-07 04:30 +0100
      Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 08:40 +0100
    Re: Copy from Firefox and paste into Terminal with Vim David Christensen <dpchrist@holgerdanske.com> - 2024-02-07 07:40 +0100

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#267122 — Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from Firefox and paste into Terminal with Vim]

Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > I have not said it is more “standard for terminals”, I have that it
> > is more “standard” fullstop. It is more standard by the virtue of
> > having worked for decades, C-Ins S-Ins S-Del existed way before the
> > C-C C-V C-X tryptich, and still working today in most contexts.  
> 
> Indeed, IIUC these key bindings were part of the CUA standard:
> https://en.wikipedia.org/wiki/IBM_Common_User_Access

Indeed and CTRL-C & friends first appeared as Apple-C on the Lisa, it
seems and were appropriated by Microsoft after a while:

https://www.howtogeek.com/804030/the-origins-of-ctrlc-ctrlv-ctrlx-and-ctrlz-explained/

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

#267117 — Re: xterm PRIMARY and CLIPBOARD selection [was: Re: Copy from Firefox and paste into Terminal with Vim]

On 07/02/2024 19:20, Nicolas George wrote:
> Max Nikulin (12024-02-07):
>> It may be a convention for applications other than terminals, however I am
>> unsure what "standard" means for terminals.
> 
> I have not said it is more “standard for terminals”, I have that it is
> more “standard” fullstop. It is more standard by the virtue of having
> worked for decades, C-Ins S-Ins S-Del existed way before the C-C C-V C-X
> tryptich, and still working today in most contexts.

Terminal application should leave standard hotkeys for applications 
running in terminals. It is the reason why modern terminals use 
[Ctrl+Shift+c] and [Ctrl+Shift+v] instead of conventional [Ctrl+c] and 
[Ctrl+v]. That is why I am against idea of adding [Ctrl+Insert] to xterm 
bindings.

In Emacs C-<insert> is bound to `kill-ring-save'.

> Works for me. The author of XTerm is quite reactive if you can explain
> the issue clearly, I am not surprised it was fixed.

My impression, it was a decision to support only single storage for 
handling selection. I like that it was changed.

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

#267118 — C-Ins vs. C-c [was: xterm PRIMARY and CLIPBOARD selection] Firefox and paste into Terminal with Vim]

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

On Wed, Feb 07, 2024 at 01:20:19PM +0100, Nicolas George wrote:
> Max Nikulin (12024-02-07):
> > It may be a convention for applications other than terminals, however I am
> > unsure what "standard" means for terminals.
> 
> I have not said it is more “standard for terminals”, I have that it is
> more “standard” fullstop. It is more standard by the virtue of having
> worked for decades, C-Ins S-Ins S-Del existed way before the C-C C-V C-X
> tryptich, and still working today in most contexts.

C-c, C-x and C-v is latest documented for the Apple Lisa, around 1983,
although it may have stolen it from the Xerox Alto [0] [1]

C-Ins, S-Del and S-Ins are IBM CUA, around 1987.

So it's the other way around :-)

Cheers

[0] https://en.wikipedia.org/wiki/Apple_Lisa
[1] https://en.wikipedia.org/wiki/Cut%2C_copy%2C_and_paste#Popularization
[2] https://en.wikipedia.org/wiki/IBM_Common_User_Access

-- 
t

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

#267084

Greg Wooledge <greg@wooledge.org> wrote:
> On Mon, Feb 05, 2024 at 10:28:53PM -0800, David Christensen wrote:
> > Continuing from above in Vim in Insert mode, if I then
> > simultaneously press the Ctrl, Shift, and v keys, and then release
> > all keys, Vim inserts the contents of the clipboard; as confirmed
> > by:
> > 
> >     xclip -o -selection CLIPBOARD  
> 
> How's that possible?  Are you running a GUI version of vim (gvim?)
> instead of running vim in a terminal?  Or are you using an exotic
> terminal?

Wow, thanks! I learned something new.

> In xterm and urxvt, Ctrl-Shift-v is identical to Ctrl-v ("literal
> next"), so there's no way vim can distinguish the two.  And yes, I
> tested it just to be sure.  In both xterm and urxvt, vim, insert
> mode, Ctrl-Shift-v acts exactly like Ctrl-v.

So it does. How bizarre! Makes vim in an xterm unusable.

> If you're using a terminal that isn't xterm, please specify which.
> This applies in general to *any* issue that involves exotic key
> combinations, because different terminals handle them differently.

I know I don't like xterm so I never use it. I mainly use lxterminal
and sometimes gnome-terminal but they both must be 'exotic' since they
behave as David said.

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

#267086

On Tue, Feb 06, 2024 at 03:36:23PM +0000, debian-user@howorth.org.uk wrote:
> I know I don't like xterm so I never use it. I mainly use lxterminal
> and sometimes gnome-terminal but they both must be 'exotic' since they
> behave as David said.

The following NEW packages will be installed:
  libvte-2.91-0 libvte-2.91-common lxterminal

Hmm, OK, that's not bad.

First thing I try: Ctrl-v Ctrl-v (at a bash prompt).  This gives ^V as
expected.

Second thing I try: Ctrl-v Shift-Ctrl-v.  This gives a long-ish paste
of what appears to be base64-encoded content, but beginning with ^[[200~
(start of bracketed paste).  There's probably another escape sequence
at the end (end of bracketed paste?) but with no Ctrl-V acting upon it,
it's not visible.

So I guess this Shift-Ctrl-v is something that's handled directly by
the terminal emulator, and does *not* result in a byte sequence that's
interpreted by the application.  That answers one of my questions, at
least.

There is ... almost no documentation, however.  "man lxterminal" gives
a stub man page written by the Debian maintainer.  The /usr/share/doc
directory is barren as well:

unicorn:/usr/share/doc/lxterminal$ ls
changelog.Debian.gz  changelog.gz  copyright

So I guess people learn about lxterminal features like Shift-Ctrl-v by
word of mouth...?

The terminal has a menu bar with a Help option.  The Help menu has exactly
one choice: About.  About gives a popup window with a link to
<http://www.lxde.org/>.  Going there and clicking the WIKI button
leads me to <https://wiki.lxde.org/en/> which is a 404 page.

*sigh*

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

#267100

On 2/6/24 04:28, Greg Wooledge wrote:
> On Mon, Feb 05, 2024 at 10:28:53PM -0800, David Christensen wrote:
>> Continuing from above in Vim in Insert mode, if I then simultaneously press
>> the Ctrl, Shift, and v keys, and then release all keys, Vim inserts the
>> contents of the clipboard; as confirmed by:
>>
>>      xclip -o -selection CLIPBOARD
> 
> How's that possible?


Thank you for the reply.  :-)


Apparently, something in the 920M bytes of my boot file system and/or in 
the 8009M bytes of my root file system make it possible.


> Are you running a GUI version of vim (gvim?)


No.


> instead of running vim in a terminal?


I am running Vim in Terminal.


> Or are you using an exotic terminal?


I do not believe so.


> If you're using a terminal that isn't xterm, please specify which.


I used the Xfce Panel Preferences dialog to create a Launcher item with 
one Terminal Emulator item:

Name:			Terminal Emulator
Comment:		Use the command line
Command:		exo-open --launch TerminalEmulator
Working Directory:
Icon:			org.xfce.terminalemulator
Options:
     checked		Use startup notification
     unchecked		Run in terminal


I click on the panel icon to start Terminal.


> In xterm and urxvt, Ctrl-Shift-v is identical to Ctrl-v ("literal
> next"), so there's no way vim can distinguish the two.  And yes, I
> tested it just to be sure.  In both xterm and urxvt, vim, insert > mode, Ctrl-Shift-v acts exactly like Ctrl-v.


I am seeing similar behavior:

https://lists.debian.org/debian-user/2024/02/msg00276.html


> This applies in general to *any* issue that involves exotic key
> combinations, because different terminals handle them differently.


Okay.


David

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

#267078

On 06/02/2024 13:28, David Christensen wrote:
> On 2/5/24 19:03, Max Nikulin wrote:
>>     xclip -o -selection PRIMARY
>>     xclip -o -selection CLIPBOARD
> 
> That is useful.

I expected that you would try both commands when vim is unable to paste. 
It would allow to discriminate whether it is Firefox or Vim issue.

> If I start Firefox, browse to https://www.toyota.com/dealers, select the
> the first dealer contents, start Vim, press and release the double-quote 
> key, press and release the asterisk key, and press and release the p 
> key, Vim inserts a blank line.

What is the effect of ["], [+], [p] keystrokes?

>> or C-R* in insert mode. 
> 
> I do not understand your notation:
> 
>      C-R*

[Ctrl+R], [*] or [Ctrl+R], [+]

     :help i_CTRL-R

>> ... Ctrl+Shift+V

I was trying to recommend against it, despite currently bracketed paste 
is enabled by default in BASH.

https://security.stackexchange.com/questions/39118/how-can-i-protect-myself-from-this-kind-of-clipboard-abuse

As to vim docs

     :help gui-selection
     :help quoteplus

and for completeness

     :help registers

Perhaps

     :help user-manual

contains description as well

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

#267104

On 2/6/24 06:25, Max Nikulin wrote:
> On 06/02/2024 13:28, David Christensen wrote:
>> On 2/5/24 19:03, Max Nikulin wrote:
>>>     xclip -o -selection PRIMARY
>>>     xclip -o -selection CLIPBOARD
>>
>> That is useful.
> 
> I expected that you would try both commands when vim is unable to paste. 
> It would allow to discriminate whether it is Firefox or Vim issue.


I tried using those commands, but was getting confusing results.  If and 
when my Debian, X, Xfce, Terminal, and/or Vim misbehave again, I will 
see if those commands produce any clues.


>> If I start Firefox, browse to https://www.toyota.com/dealers, select the
>> the first dealer contents, start Vim, press and release the 
>> double-quote key, press and release the asterisk key, and press and 
>> release the p key, Vim inserts a blank line.
> 
> What is the effect of ["], [+], [p] keystrokes?


https://lists.debian.org/debian-user/2024/02/msg00277.html


>>> or C-R* in insert mode. 
>>
>> I do not understand your notation:
>>
>>      C-R*
> 
> [Ctrl+R], [*] or [Ctrl+R], [+]
> 
>      :help i_CTRL-R


In command mode:

* Pressing Ctrl+R causes the bottom line to say:

Already at newest change

* Pressing Ctrl+R then + causes the cursor to move down one line.

* Pressing Ctrl+R then * causes the bottom line to say:

search hit BOTTOM, continuing at TOP


In insert mode:

* Pressing Ctrl+R causes the following two characters to be inserted 
into columns 53 and 54 of the bottom line:

^R

* Pressing Ctrl+R then + causes the two characters to be removed from 
the bottom line

* Pressing Ctrl+R then * causes the two characters to be removed from 
the bottom line


>>> ... Ctrl+Shift+V
> 
> I was trying to recommend against it, despite currently bracketed paste 
> is enabled by default in BASH.


https://lists.debian.org/debian-user/2024/02/msg00276.html


> https://security.stackexchange.com/questions/39118/how-can-i-protect-myself-from-this-kind-of-clipboard-abuse


Yuck.


I wonder if the https://www.toyota.com/dealers content I was attempting 
to paste into Vim contained exploits (?).  I have rebooted several 
times; perhaps the effects were not persistent (?).  Toyota's web site 
is different today; perhaps Toyota removed the exploits (?).


I wonder if the following will display exploits (?):

$ xclip -o -selection PRIMARY

$ xclip -o -selection CLIPBOARD


I wonder if my Vim has blocked "+p and "*p as a means to protect against 
clipboard attacks?


> As to vim docs
> 
>      :help gui-selection
>      :help quoteplus


https://lists.debian.org/debian-user/2024/02/msg00277.html


> and for completeness
> 
>      :help registers


It seems that I have been conflating the terms and concepts "buffer" and 
"register".


> Perhaps
> 
>      :help user-manual
> 
> contains description as well


Vim has more features than I know or use.


David

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

#267030

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

On Mon, Feb 05, 2024 at 03:14:45PM -0800, David Christensen wrote:
> debian-user:
> 
> I have a laptop with:

[copy in Firefox, paste in vim]

> I am unable to determine if the problem is Firefox, Vim, or something else.

Are you able to paste into another application?

Vim has changed its defaults a while ago in an annoying way.

Try ":set mouse=" and see whether it helps. Perhaps it's that.

Cheers
-- 
t

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

#267035

On 2/5/24 21:45, tomas@tuxteam.de wrote:
> On Mon, Feb 05, 2024 at 03:14:45PM -0800, David Christensen wrote:
>> debian-user:
>>
>> I have a laptop with:
> 
> [copy in Firefox, paste in vim]
> 
>> I am unable to determine if the problem is Firefox, Vim, or something else.
> 
> Are you able to paste into another application?


Thank you for the reply. :-)


I am not aware of any problems pasting into other applications, just 
pasting into Vim.


> Vim has changed its defaults a while ago in an annoying way.
> 
> Try ":set mouse=" and see whether it helps. Perhaps it's that.


I am unable to correlate that Vim setting change to the Vim paste problems.


David

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

#267038

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

On Mon, Feb 05, 2024 at 11:07:53PM -0800, David Christensen wrote:
> On 2/5/24 21:45, tomas@tuxteam.de wrote:

[...]

> I am not aware of any problems pasting into other applications, just pasting
> into Vim.
> 
> 
> > Vim has changed its defaults a while ago in an annoying way.
> > 
> > Try ":set mouse=" and see whether it helps. Perhaps it's that.
> 
> 
> I am unable to correlate that Vim setting change to the Vim paste problems.

Pity. In my case it does help, but my setup is rather exotic
these days (I use X's primary selection as far as possible,
some brain dead applications don't grok that anymore).

Hope you find a solution

Cheers
-- 
t

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

#267040

David Christensen wrote:
> On 2/5/24 21:45, tomas@tuxteam.de wrote:
> > Try ":set mouse=" and see whether it helps. Perhaps it's that.

That's the way. That's the fix for the root cause.

> I am unable to correlate that Vim setting change to the Vim paste problems.

But it's vim, which is changing the way how Copy&Paste is handled for its input.

Best regards,
	Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

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

#267101

On 2/6/24 00:12, Klaus Singvogel wrote:
> David Christensen wrote:
>> On 2/5/24 21:45, tomas@tuxteam.de wrote:
>>> Try ":set mouse=" and see whether it helps. Perhaps it's that.
> 
> That's the way. That's the fix for the root cause.


Thank you for the reply.  :-)


Currently, Firefox, Vim, select, copy, and/or paste seem to be behaving. 
  If and when the gremlins wake up, I'll try your suggestion.


David

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

#267070

My .vimrc contains

syntax on
set mouse-=a


And pasting works.

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Nov 20 2023 16:05:25)
Included patches: 1-2116
-- 
John Hasler 
john@sugarbit.com
Elmwood, WI USA

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

#267103

On 2/6/24 05:48, John Hasler wrote:
> My .vimrc contains
> 
> syntax on
> set mouse-=a
> 
> And pasting works.


Thank you for the reply.  :-)


If and when Firefox, Debian, X, Xfce, Terminal, and/or Vim misbehave 
again, I will try your suggestions.


> VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Nov 20 2023 16:05:25)
> Included patches: 1-2116


2024-02-06 23:39:21 dpchrist@laalaa ~
$ cat /etc/debian_version ; uname -a ; vim --version | head -n 2
11.8
Linux laalaa 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) 
x86_64 GNU/Linux
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Oct 01 2021 01:51:08)
Included patches: 1-2434


David

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

#267057

On Mon, 2024-02-05 at 15:14 -0800, David Christensen wrote:
> I am unable to determine if the problem is Firefox, Vim, or something
> else.
> 
> Comments or suggestions?

As others have written, vim has changed copy+paste defaults some time
ago. Some even call this changing defaults "they broke copy+paste" ;).
One easy thing you might want to check is if this also happens in
neovim. Neovim did not make this copy+paste change, and it might 
behave subtly different. It's quick to install and check.

/ralph

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

#267079

On 06/02/2024 18:33, Ralph Aichinger wrote:
> As others have written, vim has changed copy+paste defaults some time
> ago. Some even call this changing defaults "they broke copy+paste" 😉.

I am using vim in GUI terminal applications and I have not noticed it. 
Vim is a rare application that provides access to both PRIMARY_SELECTION 
and CLIPBOARD out of the box. E.g. in Emacs it is necessary to configure 
custom bindings, using existing user options you can choose any, but not 
both.

P.S.

Concerning set "mouse=", I usually use it, but even when mouse handling 
is active in terminal, it is possible to hold [Shift] to get mouse 
events handled by terminal instead of Vim or another application running 
in terminal.

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

#267080

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

On Tue, Feb 06, 2024 at 09:31:33PM +0700, Max Nikulin wrote:

[...]

> Concerning set "mouse=", I usually use it, but even when mouse handling is
> active in terminal, it is possible to hold [Shift] to get mouse events
> handled by terminal instead of Vim or another application running in
> terminal.

Indeed! Thanks for this one, Max :-)

Cheers
-- 
t

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

#267089

On Tue, 2024-02-06 at 21:31 +0700, Max Nikulin wrote:
> is active in terminal, it is possible to hold [Shift] to get mouse 
> events handled by terminal instead of Vim or another application
> running in terminal.

I think pressing shift does not work here in e.g. gnome-terminal,
because there paste is Shift-Ctrl-V and interpreted by gnome-terminal.
Have not tried it though, vim taking care of the mouse is just nuts
in my opinion ;)

/ralph

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

#267094

On 07/02/2024 00:35, Ralph Aichinger wrote:
> On Tue, 2024-02-06 at 21:31 +0700, Max Nikulin wrote:
>> is active in terminal, it is possible to hold [Shift] to get mouse
>> events handled by terminal instead of Vim or another application
>> running in terminal.
> 
> I think pressing shift does not work here in e.g. gnome-terminal,
> because there paste is Shift-Ctrl-V and interpreted by gnome-terminal.
> Have not tried it though, vim taking care of the mouse is just nuts
> in my opinion ;)

[Ctrl+Shift+V] is not a mouse event. Consider vim with enabled mouse on 
a remote host when X11 forwarding is disabled in ssh. Local selection is 
not available through + and * registers. It is handy to use Shift to be 
able to select some text (unless it is multiline text in a vertically 
split window) or to paste in insert mode by Shift+middle mouse button.

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

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

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

csiph-web