File position reverted by other joe instances
Sorry, double post due to network error.
File position reverted by other joe instances
File position reverted by other joe instances
Undo history weirdness; ^C drops changes without asking for confirmation
... (nitpicking) or maybe clear all the bits using Cb &= ~0xC3 and then set the two low ones with Cb |= 3. This is more consistent in the sense that the same bitmask 0xC3 is used throughout the method. Also, I didn't mention it explicitly, but this last paragraph of my previous post explains why "release" events of left scrolling become right scrolling instead, resulting in back-n-forth pairs in some terminals.
Update or drop xterm patch and related code
Cb contains the button number, as encoded in decimal ASCII as the first parameter if the 1006 extension is supported by the terminal, or the first rawy byte minus 32 with the legacy byte-based protocol if 1006 is not supported by the terminal. Cb's value consists of the following bits: - bit 7 (128): button value bit 3 (8) - bit 6 (64): button value bit 2 (4) - bit 5 (32): drag - bit 4 (16): ctrl - bit 3 (8): alt - bit 2 (4): shift - bit 1 (2): button value bit 1 (2) - bit 0 (1): button value bit...