Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • Thanks for the investigation and very detailed answer. However, you lost me with the discussion about Meta. I understand ~Meta <Btn1Down>:select-start() as meaning btn1 triggers select-start() unless the Meta modifier is on (mod2 for you, mod1 for me). I don't understand how that can allow me to do selection with shift and numlock on. I don't understand the couple of mode-switches part either. I can't test Alt+Btn1 as that's intercepted by my window manager to move windows. Commented Oct 31, 2020 at 6:29
  • After switching to a different window manager, after \e[?1000h, I see \e[M(xy upon Meta+btn1 (with numlock or not), \e[M,xy with Meta+Shift+btn1 (with numlock or not), and again \e[M$xy with Shift+btn1 (with numlock only). I don't see any other option but to disable numlock to be able to do mouse selection with Shift. Commented Oct 31, 2020 at 6:47
  • FWIW, according to invisible-island.net/xterm/ctlseqs/…, xterm understands mod1 as Meta, which is consistent with those ( (0b101000) and , (0b101100) above when I press Alt. Commented Oct 31, 2020 at 7:07
  • It does that, in mouse-button events, however for other inputs (such as function-keys), I'd rather distinguish alt and meta. I suppose this is another opportunity to improve the FAQ. It's not clear to me why you're pressing numlock. Commented Oct 31, 2020 at 13:27
  • 1
    I see (thanks for the clarification). I'll add yet-another-feature in 362 to make the equality-check optional, so that the older/laxer check would be the default. By the way, this is another case where that pull request would create a problem. Commented Oct 31, 2020 at 14:32