Is there a way to change how the cursor displays with [tag:gpm]? In my Debian terminal it shows up as a light grey box that's easy to keep track of, but when I use it within one of my Alpine containers it changes the color of the text its hovering over, which is very easy to lose track of. Specifically: I want the [tag:gpm] cursor to display as the solid grey box. How do I force [tag:gpm] to do this?

I have a Linux console running in a virtual machine (QEMU/KVM). Inside the VM I use GPM in order to select and paste text with the mouse. However, when I enter the VM's spice virt-viewer window in my graphical desktop the graphical mouse cursor of the desktop is completely at a different position than the GPM mouse cursor. That is annoying and it means that some areas of the VM's text window cannot be reached without entering and exiting the spice window several times. **How do I align/synchronise the mouse cursors of spice/desktop and GPM?** I cannot install an additional program in the VM because it is a server. It must work with GPM alone. Perhaps QEMU needs some config options?

Slacware64-current (july 2020) Kernel 5.4.50 Hi: This is from gpm's man page: [code] OPERATION To select text press the left mouse button and drag the mouse. To paste text in the same or another console, press the mid‐ dle button. The right button is used to extend the selection, like in `xterm'. Two-button mice use the right button to paste text. [/code] I have a two-button mouse (actually a touchpad, this is a laptop). I am in a text console, say /dev/tty6, and I select an area with the left button. Now I press the right button... and nothing happens. Possible cause?

I use libgpm in order to read mouse events in my console application. It works fine if started right from the shell. It doesn't receive any mouse events if started from mc (midnight commander). Problem is related to pseudo terminal mc creates for my process. I can semi-solve this problem by forcing gpm to use specified console screen passed as second argument to Gpm_Open (instead of 0 - auto?). int Gpm_Open(Gpm_Connect*,int); Is there any way to know which virtual console screen should I use when running on pseudo tty (created by mc)? I've considered using active console but it may not be the one my application is running on. Probably traversing process tree and checking if its TTY is a real console would work but I don't know how to get tty(name) for given pid and I'm afraid I'd need elevated privileges for that. Or hopefully is there any simpler workaround? Edit: I've just noticed that starting my process from mc but via sudo (using command line) without forcing gpm to use patricular vc screen - simply works!

I am running Tmux 2.2 on Arch Linux. I tend to use it from a raw TTY console, rather than an xterm in a window manager. I have GPM installed and running, however I cannot seem to get GPM and Tmux to work together at all. I've enabled the mouse functions with setw -g mouse on however, none of the operations actually function. Selecting a panel/window doesn't work; and I cannot use the mouse in mouse-enabled applications running in Tmux, such as MidnightCommander. MC works with the mouse outside of Tmux, but not inside. Is there a way to get GPM and Tmux to get along? Or does tmux rely on X11 to handle the mouse interaction? Thanks in advance!

I noticed it when installing gentoo https://wiki.gentoo.org/wiki/GPM But I can't figure out of it's possible to get it to work outside of a tty. I'm using GNOME-Terminal if that matters.

Is there some general mechanism missing in text mode consoles but present in GUI terminals that I can enable for mouse-supporting applications? By "general" I mean not per-application (not application-specific). For example, aptitude, finch, w3m, etc. understand clicks in GUI terminals but not in Linux consoles with GPM. They seem to share the same problem. Since aptitude (etc.) *does* include mouse support (it's just inactive in text mode consoles for some reason), the aptitude case should not be seen as "magically adding a feature that an application doesn't support". I have mouse support in Aptitude in a GUI terminal; I have GPM running on a Linux console; how do I get mouse support in Aptitude in the console? I think there is a switch between GUI terminals and consoles (a feature that makes the difference). I guess we've all encountered a few more of those GUI/console "switches" (and I have a few more of these questions). A "switch" may affect many applications, thus becoming a broader, system-wide issue, yet the issue itself can be specific, which I hope may validate my question. If not, for simplicity, we could make this question about aptitude and gpm. Any answer may still be a useful lead. At least it helps me learn more about getting the TTY as mouse-aware as it can get. My purpose was to make console editing more "natural-feeling", with a special focus on nano and readline. Nano and mc were not a good lead; they are just isolated console workaround cases, not mouse support vs no support cases. Readline turned out to be a more complicated case, so it wasn't as representative as I'd hoped. However, after one gets it to work, it probably hits the same "switch". Mouse reporting events seem to be encoded differently in the console.