惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
J
Java Code Geeks
IT之家
IT之家
Last Week in AI
Last Week in AI
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
B
Blog RSS Feed
P
Proofpoint News Feed
博客园 - Franky
MongoDB | Blog
MongoDB | Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园 - 【当耐特】
Microsoft Security Blog
Microsoft Security Blog
I
InfoQ
B
Blog
Stack Overflow Blog
Stack Overflow Blog
Martin Fowler
Martin Fowler
博客园 - 聂微东
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Apple Machine Learning Research
Apple Machine Learning Research
大猫的无限游戏
大猫的无限游戏
U
Unit 42
aimingoo的专栏
aimingoo的专栏

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Constraints Are Interfaces: What the TrackPoint Teaches A...
rbcn · 2026-06-19 · via DEV Community

rbcn

The ThinkPad That Was Supposed to Be a Side Machine

I bought a cheap used laptop as a casual work machine.

It was a ThinkPad X1 Carbon Gen 7. I installed Linux Mint and meant to use it as a secondary machine: light research, writing, a bit of work on the go. Nothing more than that.

Then it turned out to be better than expected.

Thin. Light. Good keyboard. Linux Mint ran without much drama. For a corporate lease-return laptop, it was not living out its retirement. It was still a perfectly capable working machine. Before I knew it, the side machine had become my main one.

But one thing kept bothering me.

The touchpad.

Sometimes Convenience Gets in the Way

The touchpad itself was not bad.

If anything, it was normally useful. It scrolls. It handles fine movements. On a modern laptop, it is the expected pointing device.

But in my own use, misfires started to stand out.

While writing, my palm or the base of my thumb would touch it without me noticing. The cursor would jump. I would type into the wrong place. A selection would change unexpectedly.

A small accident.

But for a machine used mainly for writing, it mattered.

Then I remembered something.

My first laptop had also been a ThinkPad: an IBM ThinkPad R31. Back then, there was no giant modern touchpad experience. There was a red dot in the middle of the keyboard, and you moved the pointer by pushing it.

So maybe I should simply go back.

Disable the touchpad. Return to the TrackPoint.

At First, It Was Just touchpad-off

The first step was simple.

I checked the touchpad name with xinput list.

SYNA8004:00 06CB:CD8B Touchpad

Then I disabled it.

xinput disable "SYNA8004:00 06CB:CD8B Touchpad"

That alone changed the feel of the machine.

My hands stayed near the home position. Pointer movement converged on the red dot. As a writing machine, the whole posture became more consistent.

At first, I treated this as a simple toggle.

#!/usr/bin/env bash
xinput disable "SYNA8004:00 06CB:CD8B Touchpad"

And if needed, turn it back on.

#!/usr/bin/env bash
xinput enable "SYNA8004:00 06CB:CD8B Touchpad"

This was the world of touchpad-off.sh and touchpad-on.sh.

At that point, it was still just a convenience setting.

Colliding with an Old X11 UX

But disabling the touchpad was not the end of it.

To scroll with the TrackPoint, you hold the middle button and push the red dot. That gesture is very ThinkPad-like. But on Linux / X11, the middle button also has another meaning.

Middle-click paste.

select text
↓
it enters PRIMARY selection
↓
middle click
↓
paste

This is an old X11 convenience. For people who know and use it, it is fast. But it was not part of the UX I had internalized when I first used a ThinkPad on Windows XP.

For my body, the middle button was not a paste button.

It was the button for TrackPoint scrolling.

So accidents happened.

I would be reading code or text. I would scroll. Some text I had selected somewhere would be pasted unexpectedly. Different from cursor jumps, but still another kind of input-path noise.

I could not simply kill the middle button itself. I needed it for scrolling.

The thing to kill was not the button, but its interpretation as paste.

xfconf-query -c xsettings -p /Gtk/EnablePrimaryPaste -n -t bool -s false 2>/dev/null \
  || xfconf-query -c xsettings -p /Gtk/EnablePrimaryPaste -s false

However, this only expressed a policy for GTK / Xfce applications. It did not remove middle-click paste from X11 as a whole. Electron apps, terminals, and some editors could still interpret Button2 on their own.

So in the end, I stopped delivering Button2 from the TrackPoint device to applications.

xinput set-button-map "TPPS/2 Elan TrackPoint" 1 0 3 4 5 6 7

The 0 means: do not send the middle button to applications. At the same time, libinput can still keep that physical button as the modifier for TrackPoint scrolling.

xinput set-prop "TPPS/2 Elan TrackPoint" "libinput Scroll Method Enabled" 0 0 1
xinput set-prop "TPPS/2 Elan TrackPoint" "libinput Button Scrolling Button" 2

Now the middle button remains for scrolling. Middle-click paste is sealed away. Paste is consolidated into Ctrl+V / Ctrl+Shift+V.

It Became Mode-In

At this point, what I was doing was no longer just turning the touchpad on and off.

Disable the touchpad
Disable PrimaryPaste
Fix the TrackPoint as the primary input device
Keep the middle button for scrolling
Stop delivering Button2 to applications
Move paste into explicit keyboard shortcuts

This was a transition into an input mode.

So I renamed the script.

Not touchpad-off.sh, but thinkpadder-mode-in.sh.

#!/usr/bin/env bash
set -euo pipefail

TOUCHPAD="SYNA8004:00 06CB:CD8B Touchpad"
TRACKPOINT="TPPS/2 Elan TrackPoint"
PRIMARY_PASTE="/Gtk/EnablePrimaryPaste"

xinput disable "$TOUCHPAD" 2>/dev/null || true

xfconf-query -c xsettings -p "$PRIMARY_PASTE" -n -t bool -s false 2>/dev/null \
  || xfconf-query -c xsettings -p "$PRIMARY_PASTE" -s false

if xinput list --name-only | grep -Fxq "$TRACKPOINT"; then
  xinput set-prop "$TRACKPOINT" "libinput Scroll Method Enabled" 0 0 1 2>/dev/null || true
  xinput set-prop "$TRACKPOINT" "libinput Button Scrolling Button" 2 2>/dev/null || true
  xinput set-button-map "$TRACKPOINT" 1 0 3 4 5 6 7 2>/dev/null || true
fi

Then I registered it with Xfce autostart.

[Desktop Entry]
Type=Application
Name=ThinkPadder Mode In
Comment=Enter TrackPoint-first ThinkPad input mode
Exec=/home/rbcn2000/.local/bin/thinkpadder-mode-in.sh
OnlyShowIn=XFCE;
X-GNOME-Autostart-enabled=true
Terminal=false

Once the machine starts, it enters ThinkPadder Mode automatically.

Constraints Are Interfaces

This is not for everyone.

Many people are better off with the touchpad. Some people love X11 middle-click paste. Some people want the escape route visible at all times.

But for me, cutting off the retreat and fixing the operation path was rational.

I wanted fewer misfires. I wanted a stable input posture. I wanted to return to a TrackPoint-centered bodily feel. For that goal, reducing options was not merely making the machine less convenient.

The constraint was the interface.

UX is not only about adding what users can do. Sometimes the body stops hesitating because something becomes impossible. Disable the touchpad, and the hand returns to the red dot. Stop delivering Button2 to applications, and the middle button becomes trustworthy as a scrolling modifier.

Customization is not only about making the tool adapt to you.

There is also a kind of customization where you make your body adapt to the tool's philosophy.

The TrackPoint is not a substitute for a mouse.

It is an extension of the keyboard.

If you see it that way, disabling the touchpad is not just nostalgia. It is a way to govern input paths and support embodied use.


This essay looked at TrackPoint UX through the lens of constraints and embodied tool design.

The more personal memory behind the same experience is here.

https://fragmentofview.rbcn.cc/posts/en/red-dot-in-the-middle-touchpad/

Japanese version:

https://emptytheory.rbcn.cc/ja/constraints-are-interfaces-trackpoint-ux/