About: Using the mouse for Vim in an xterm

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: Using the mouse for Vim in an xterm Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

The first problem is caused by line numbering, which I keep enabled at all times. :set number Normally, if you try to copy text out of the xterm that vim is running in, you'll get the text as well as the numbers. The GUI version gets this right: it only selects the text, keeping the line numbers out of the picture. But I don't want the GUI version. So instead, I added this to my vimrc: :set mouse=a Much better. You can also selectively enable mouse support for specific modes only by using something other than 'a' (for 'all'). $ xrdb -load .Xresources :map [62~ " etc " ...

Attributes	Values
rdfs:label	Using the mouse for Vim in an xterm
rdfs:comment	The first problem is caused by line numbering, which I keep enabled at all times. :set number Normally, if you try to copy text out of the xterm that vim is running in, you'll get the text as well as the numbers. The GUI version gets this right: it only selects the text, keeping the line numbers out of the picture. But I don't want the GUI version. So instead, I added this to my vimrc: :set mouse=a Much better. You can also selectively enable mouse support for specific modes only by using something other than 'a' (for 'all'). $ xrdb -load .Xresources :map [62~ " etc " ...
Version	6(xsd:integer)
dbkwik:vim/property/wikiPageUsesTemplate	dbkwik:resource/fCAJ4KMN7sC-cxnOSWi1_Q== dbkwik:resource/1UkzPUuF-PpuM0-NgABghA== dbkwik:resource/DSqHV0Kw5d1d-hQlD2avAw==
Previous	469(xsd:integer)
Category	Mouse Terminals
Author	pagaltzis
Complexity	basic
Created	2003(xsd:integer)
ID	471(xsd:integer)
NEXT	472(xsd:integer)
Rating	55(xsd:integer)
abstract	The first problem is caused by line numbering, which I keep enabled at all times. :set number Normally, if you try to copy text out of the xterm that vim is running in, you'll get the text as well as the numbers. The GUI version gets this right: it only selects the text, keeping the line numbers out of the picture. But I don't want the GUI version. So instead, I added this to my vimrc: :set mouse=a Much better. You can also selectively enable mouse support for specific modes only by using something other than 'a' (for 'all'). Now although I'm more of a keyboarder, when I juggle text between X apps (or maybe between xterms), it's just more convenient and efficient to keep my hands on my mouse, since they're there anyway. Now, if you own a moderately recent model, you'll know this lovely little wheel they have (which usually also doubles as mouse button 2). Rolling it scrolls the window in GUI vim, which simplifies life when selecting several, distant passages to paste one after the other. But I don't want to use the GUI vim - you can imagine my delight when I ran across this in the vim documentation: It involves adding a couple mappings to your vimrc and corresponding VT100 translations to your .Xresources file as a prerequisite. Don't forget $ xrdb -load .Xresources after you edit the file. The running xterm will not heed the changes; you need to open a new one to see the effect. The wheel may not work with the mappings as described in the helpfile. They worked without a hitch for me at first (using Xfree 4.1 then), but broke after I upgraded my distro. Whether it was the switch to 4.3 on this binary has been built with different options, I don't know. At any rate, I had to experiment a bit with the list from After a bit of trial and error, I finally fixed them by substituting for : :map [62~ " etc " ... Done. Load a large text file and marvel at mousewheel scrolling.

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software