Tag Info

Hot answers tagged

16

Mouse scrolling and elevators will work if you enable them in your .screenrc. Screen FAQ Q: My xterm scrollbar does not work with screen. A: The problem is that xterm will not allow scrolling if the alternate text buffer is selected. The standard definitions of the termcap initialize capabilities ti and te switch to and from the alternate ...


16

Try the following command : xdotool getmouselocation 2>&1 | sed -rn '${s/x:([0-9]+) y:([0-9]+) .*/\1 \2/p}' See http://www.semicomplete.com/projects/xdotool/


14

Assuming your GUI is X-based (as almost all UNIX GUIs are), use xinput. First, list your devices: $ xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Windows mouse id=6 [slave pointer (2)] ⎣ Virtual ...


14

Start the program xev in a terminal. Move the mouse inside the xev window; you'll see a lot of stuff scroll by. Press each button in turn. Then switch back to the terminal window and press Ctrl+C. xev shows a description of each input event, in particular ButtonPress and ButtonRelease for mouse clicks (you'll also see a number of MotionNotify for mouse ...


13

On modern-ish X.org installations, there is an XF86Ungrab keysym, which causes the server to release all active pointer or keyboard grabs. You can make the server break all grabs by generating the keysym either with a command or with the keyboard. With xdotool: xdotool key XF86Ungrab On some systems, the XF86Ungrab keysym is bound to the key combination ...


12

First thing that we need to accomplish is turning off mouse, but only in X. For this we could use xinput. We need to discover input devices that are connected to computer (to X server): pbm@tauri ~ $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave ...


12

On most systems :set mouse=a will enable your mouse inside vim even on the console. I personally prefer using the vim keybindings, but some variant on: :vmap <C-c> "*y :imap <C-v> <ESC>"*gPa :nmap <C-v> "*gP Will probably do what you want for ctrl-c and ctrl-v


11

In more recent gnome versions (e.g., gnome-shell), you need to use this instead: gsettings set org.gnome.desktop.wm.preferences resize-with-right-button true


10

xdotool exposes the pointer location (xdotool getmouselocation). None of xdotool, xwininfo or wmctrl appear to have a way to match a window by a screen position where it's visible. The underlying X library call is XQueryPointer (corresponding to a QueryPointer message). Here's a simple Python wrapper script around this call (using ctypes). Error checking ...


9

The xwininfo command gives this kind of output, but you do have to click on the window you want info on: % xwininfo xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0xa0000d "flask" ... So doing: xwininfo | grep 'Window id:' might give you something ...


9

One more option is xinput. For instance, xinput test 8 would write motion a[0]=496 a[1]=830 motion a[0]=496 a[1]=829 motion a[0]=496 a[1]=832 motion a[0]=496 a[1]=834 upon mouse movement, where "8" is my mouse device number. Use xinput --list to find out the number of your mouse among devices.


8

For linux (or at least the Debian family of distributions, e.g Ubuntu) there are the vim-gnome and vim-gtk packages. For Mac there is MacVim, for Windows gvim. Both are linked from the vim download page.


6

That's just the way that the PS/2 port works. Unlike the USB, the PS/2 was not designed to be hot-plugged. If you need the hot-plugging capability, use a USB mouse. Otherwise, there is no guarantee that any solution will work consistently.


6

You can set this property with xinput. Run xinput list to see the list of connected input devices. Note the exact name or the number of the device corresponding to your mouse (not the “Virtual core pointer”, but something like “Logitech USB-PS/2 Mouse M-BA47”). The name depends on your mouse model; I think the number is assigned dynamically, so you might ...


6

xinput --set-int-prop is deprecated. You should use --set-prop instead. Also, xinput --enable [device] and xinput --disable [device] can be used to enable and disable devices respectively. Here is a shell script I use to enable, disable, and toggle my laptop's touchpad: #!/bin/bash # Enables, disables, or toggles device device='AlpsPS/2 ALPS GlidePoint' ...


5

On my ThinkPad X220T running GNOME 3 it's pretty easy to be typing along and accidentally bump the touchpad, causing some window other than the one you're typing into to be raised. Ostensibly, the solution to this problem is to click your name in the upper right, then click "System Settings", then "Mouse and Touchpad", and then "Disable touchpad while ...


5

mouse support is disabled by default, so something is turning it on. Likely the reason your set mouse= is failing is because it's running before whatever is turning it on. I'd look through the rest of your vimrc, and possibly the system wide vimrc (/etc/vim/vimrc is a standard location). As a last resort, you can do this really ugly hack which will cause ...


5

The feature you are talking about is called Auto-Scrolling. It lets you press & hold the middle mouse button and move your mouse to scroll smoothly. In Linux, the default behavior for this action (pressing middle mouse button) is generally used for pasting text. However, there is a preference setting in Firefox and an extension available for ...


5

You cannot map two physical buttons to the same logical button. All you can do is swap the buttons (echo 'pointer 1 7 3 4 5 6 2' | xmodmap -). This is a low-level limitation of X11. As stated in the documentation of XSetPointerMapping: However, no two elements can have the same nonzero value, or a BadValue error results. The best you can do is to use a ...


5

You can use xinput. >xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Mouse0 id=6 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST ...


5

Go to Settings->Edit Current Profile. Select the Mouse tab. There's a check box there: Allow Ctrl+scrollwheel to zoom text size. Untick that and click Apply.


4

If I understood your needs you have to bind one screen, keyboard and one mouse to one ServerLayout and the others to the second one. http://cambuca.ldhs.cetuc.puc-rio.br/multiuser/ Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section ...


4

I've never tried, but these instructions for Ubuntu look plausible, and mostly distribution-independent. Add a section for the joystick in /etc/X11/xorg.conf. (If you don't have one, generate it with Xorg -configure.) The critical line is the SendCoreEvents option, which makes the joystick events move the mouse pointer. If your distribution splits up X11 ...


4

Recent versions of X (X.org server ≥1.11) support several debugging keysyms, introduced in this commit. When triggered, these perform actions related to grabs. By default (at least in recent versions), these are disabled (absent from the default keymap). However, if you have xdotool installed, it is possible to call them, by executing on the command-line: ...


4

Having the middle button paste is a unix user interface standard, like having the left button select or activate, and the right button do something else (such as extending, toggling, firing up a menu, …). You'll find it bound to pasting in most unix applications. If your problem is that your mouse is overly sensitive when you put your finger on the wheel, I ...


4

You can use gconf-editor for this. Enable this setting: /apps/metacity/general/resize_with_right_button


4

I had thought someone told me or I heard somewhere that xorg by default supports keyboard driven mouse emulation out of the box. The movement, etc. is bound to the numpad keys. This article I dug up quick seems to indicate I have heard correctly. No direct experience, so this may be incorrect. See ...


4

You do it with X resources. I have a file, .Xresources, that contains these xterm-related resources: XTerm*VT100.cutNewLine: false XTerm*VT100.cutToBeginningOfLine: false XTerm*VT100.charClass: 33:48,35:48,37:48,42:48,45-47:48,64:48,95:48,126:48 In my .xinitrc file, I have some line that merge in those resources: if [ -f $userresources ]; then ...


4

This Windows feature has never really made its way into the Unix world. In the Unix world, the primary purpose of the middle mouse button is to paste the clipboard content (or more precisely, text selected with the mouse, which is auto-copied). A couple of cross-platform applications such as Firefox and Chrome that support Linux-style middle mouse button ...


3

There is anecdotal evidence that restarting the X Server or switching to a a different virtual terminal and back will cause PS/2 devices to be re-detected. I don't have a PS/2 device to test with at the moment though but it may just work.



Only top voted, non community-wiki answers of a minimum length are eligible