From: Gabriel Ivăncescu Subject: Re: [PATCH v2 4/8] shell32/autocomplete: Don't autocomplete at all on most control characters Message-Id: Date: Fri, 21 Sep 2018 14:50:45 +0300 In-Reply-To: <20180921114426.GS3601@merlot.physics.ox.ac.uk> References: <0d9f77e0aa067a3883af70444ae00efa535bc668.1537444354.git.gabrielopcode@gmail.com> <34e55051-197e-e84a-bfa4-6844e3c37506@codeweavers.com> <20180921104522.GO3601@merlot.physics.ox.ac.uk> <20180921113206.GQ3601@merlot.physics.ox.ac.uk> <20180921114426.GS3601@merlot.physics.ox.ac.uk> On Fri, Sep 21, 2018 at 2:44 PM, Huw Davies wrote: > > Doesn't sound like it would be too hard to test (just send some WM_CHARs > to the edit). > > Huw. I mean, they don't work on our/Windows edit control implementation (might depend on styles, I don't know), but some apps might subclass the edit control before AutoComplete on them and make them useable. I was just wondering since tab / newline / carriage return actually do "something" to the text in question like backspace, so that's why I had doubts whether we should process them or not.