Tag Info

Hot answers tagged

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 ...


13

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 ...


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


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 ...


11

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 ...


9

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

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 ...


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

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.


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

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 ...


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

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

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

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 ...


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

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 ...


4

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 ...


3

The answered question using xinput is the right one, but here is a quick one if all you are looking for is a simple screensaver type lock. I wrote this back in the '90s, and all it does is eat the X server's keyboard and mouse events, until you type the password. No feedback at all other than exiting when you type it correctly. ...


3

If you are using KDE's own builtin screensaver, I'm not sure... however, if you are using xscreensaver or are interested in using xscreensaver the following should help. Using xscreensaver you can adjust the number of pixels that the mouse must move before deactivating the screensaver; not sure about completing disabling the mouse though. If you are not ...


3

One interesting possibility I forgot is what Tyler Szabo's answer to my question Multiseat gaming? @gaming.SE suggests: I would use VMWare. This might be possible with just VMWare player (you will need to be able to allocate a mouse to a single VM), or you might need to try VMWare workstation (for which I'm quite sure it works). The hardware/software you ...


3

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 ...


3

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: ...


3

better format: (sry 4 double answer) go to settings> setting editor click on xfwm4 in 'chanel side bar click on general to display tree list and find one called 'mouesewheel_rollup' click on to highlight and click edit icon at top of window its a Bool so all you need to do is uncheck enable box. save from: ...


3

I have this problem as well. I think it's related to the bug herein: http://osdir.com/ml/blfs-support/2011-12/msg00059.html The problem seems to be related to specific functionality in gtk 3.0, likely related to resizing the window or making the resize grip appear: I've gotten this behavior when I use Meta-Mouse2 to resize in Awesome. I've also seen it ...


3

I answered this on Super User, and am quoting it here: [As Gilles noted,] In fact, it is possible to do this (at least with recent versions of X). You can do this by pressing the XF86Ungrab key, introduced in this commit. By default, this keysym is not bound to any physical key or key combination (it was disabled in 2012 after it was ...


3

Sounds like an issue with a kernel module. Did you recently install any new updates or drivers? Boot up into single user or text only mode and try to remove your mouse module. In the console type: lsmod look for a module relating to mouse and trackpad such as synaptics, xf86 or touchegg, and then remove them using: sudo modprobe -r module_name then ...



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