![\"\"](\"https:\/\/c-for-dummies.com\/blog\/wp-content\/uploads\/2026\/01\/House-mouse-Mus-musculus-shutterstock_321795701-300x167.jpg\")
\nAfter I bought a mouse for my first PC, I set out to write a mouse-based program — a game. (The Microsoft Mouse manual came with the full API.) It was fun and challenging, as all programming tasks should be. Surprisingly, reading the mouse is also possible in a Linux terminal window — providing that you know the secret.
\n
\nThe secret: ANSI.<\/p>\n
Yes, just as various ANSI commands let you manipulate text output<\/a> and cursor position<\/a>, you can also use ANSI commands to read the mouse’s location, movement, and clicks in a terminal window. But this trick isn’t without its issues.<\/p>\n To start, the commands to read the mouse are not part of the original ANSI standard. They are, however, available with the xterm extensions, which are implemented in most terminal windows.<\/p>\n Like most other ANSI commands, the mouse commands are delivered by sending a specific string of characters to standard output. The sequence starts with an Escape character ( The sequence The following code implements these escape sequences as macros, mouse_enable()<\/em> and mouse_disable()<\/em>:<\/p>\n It’s important that you disable mouse tracking before the program ends. Failing to do means that mouse activity in the terminal window continues to be monitored, which can really ruin your day. (Issue the reset<\/em> command to restore the terminal to sanity.)<\/p>\n Running this program generates no output unless you click the mouse. When you do, output appears similar to this:<\/p>\n Press the Enter key to terminate the program.<\/p>\n When you click the mouse, the output you see reports the button clicked and the mouse’s location in some cryptic format. What’s better is to also issue the ANSI “any event” tracking sequence, The mouse_motion()<\/em> macro is assigned to the Each sequence output represents the mouse’s movement from one character position to the next, as well as any button clicks.<\/p>\n The output can be quite overwhelming, rapidly filling the screen. It’s also cryptic. To make the output human readable, I recommend adding a fourth macro to the code, mouse_extended()<\/em>, as shown in this final update:<\/p>\n The mouse_extended()<\/em> escape sequence is The sequences generated follow a pattern that offers the mouse's button status, row and column location on the terminal screen. I cover deciphering this information in next week's Lesson<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Yes, you can read the mouse in a terminal window. Continue reading \\e<\/code>) followed by a left bracket and a question mark. Then comes a mode value and finally a little H or little L.<\/p>\n\\e[?1000h<\/code> activates mouse tracking.
\nThe sequence \\e[?1000l<\/code> deactivates mouse tracking.<\/p>\n2026_01_31-Lesson-a.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n\r\n#define mouse_enable() printf(\"\\e[?1000h\")\r\n#define mouse_disable() printf(\"\\e[?1000l\")\r\n\r\nint main()\r\n{\r\n \/* enable mouse reporting *\/<\/span>\r\n mouse_enable();\r\n\r\n getchar();\r\n\r\n \/* clean-up *\/<\/span>\r\n mouse_disable(); \/* disable mouse reporting *\/<\/span>\r\n return 0;\r\n}<\/pre>\n^[[M ;4^[[M#;4<\/pre>\n
\\e[?1003h<\/code>, which provides more information about the mouse’s location and button status. The following code provides this update:<\/p>\n2026_01_31-Lesson-b.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n\r\n#define mouse_enable() printf(\"\\e[?1000h\")\r\n#define mouse_motion() printf(\"\\e[?1003h\")\r\n#define mouse_disable() printf(\"\\e[?1000l\")\r\n\r\nint main()\r\n{\r\n \/* enable mouse reporting *\/<\/span>\r\n mouse_enable();\r\n mouse_motion();\r\n\r\n getchar();\r\n\r\n \/* clean-up *\/<\/span>\r\n mouse_disable(); \/* disable mouse reporting *\/<\/span>\r\n return 0;\r\n}<\/pre>\n\\e[?1003h<\/code> escape sequence. When you run the program, moving the mouse immediately generates output. You see something like this:<\/p>\n^[[MCY.^[[MCZ-^[[MCZ.^[[MCY\/^[[MCX\/^[[MCW0^[[MCV0^[[MCV1^[[MCU1^[[MCU2^[[MCU1^[[MCT1^[[MCS1^[[MCS0^[[MCR0^[[M R0^[[M#R0^[[M R0^[[M#R0<\/pre>\n
2026_01_31-Lesson-c.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n\r\n#define mouse_enable() printf(\"\\e[?1000h\")\r\n#define mouse_motion() printf(\"\\e[?1003h\")\r\n#define mouse_extended() printf(\"\\e[?1006h\")\r\n#define mouse_disable() printf(\"\\e[?1000l\")\r\n\r\nint main()\r\n{\r\n \/* enable mouse reporting *\/<\/span>\r\n mouse_enable();\r\n mouse_motion();\r\n mouse_extended();\r\n\r\n getchar();\r\n\r\n \/* clean-up *\/<\/span>\r\n mouse_disable(); \/* disable mouse reporting *\/<\/span>\r\n return 0;\r\n}<\/pre>\n\\e[?1006h<\/code>. Here’s a sample run with this macro issued:<\/p>\n^[[<35;49;15M^[[<35;49;16M^[[<35;49;17M^[[<35;48;17M^[[<35;48;16M^[[<35;47;16M^[[<35;47;17M^[[<35;47;16M^[[<35;46;16M^[[<0;46;16M^[[<0;46;16m<\/pre>\n