Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752472AbdC0Kfy (ORCPT ); Mon, 27 Mar 2017 06:35:54 -0400 Received: from tartarus.angband.pl ([89.206.35.136]:57204 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752086AbdC0Kfp (ORCPT ); Mon, 27 Mar 2017 06:35:45 -0400 Date: Mon, 27 Mar 2017 12:35:17 +0200 From: Adam Borowski To: Greg Kroah-Hartman , Jiri Slaby , linux-kernel@vger.kernel.org Subject: [PATCH 0/2] vt: mouse selection word boundaries Message-ID: <20170327103517.tlvzfuobtjxk2vci@angband.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 870 Lines: 20 Hi! Here's a couple of really low priority fixes to how "word chars" for mouse selection are determined. Patch 1 (adds "-./") is an epitome of "apply if bored": for two decades, only gpm used this, and it always ignored the defaults. Bill Allombert made a second implementation, "consolation", and we wasted a bit of time figuring out why mouse selection is so limited. As consolation now overrides the defaults too, this patch will be helpful only for whoever makes a third user of this code... Patch 2, besides making a handful of non-ASCII symbols work the same as everything else, also stops people from mysteriously losing that 'ü' after naive gpm -l "-A-Za-z0-9_./". -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!