From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Additional cleanup around xterm-mouse Date: Sun, 20 Dec 2020 09:07:43 -0500 Message-ID: References: <83o8jupnqd.fsf@gnu.org> <838savys2v.fsf@gnu.org> <3e3933d8ec1d5d3f6809385a8ac5f447@finder.org> <83mtz1moa5.fsf@gnu.org> <0ea60a4f2a7fb0698f84ac5957cafef3@finder.org> <83mtyxgzck.fsf@gnu.org> <2eac7957a7c20af3517a3ad0862a5b39@finder.org> <106c6d31ef09b83042ef0fab5ac0ed88@finder.org> <505d1b561cde375d1c6a55a738cd553d@finder.org> <83ft48csj5.fsf@gnu.org> <83bleptzng.fsf@gnu.org> <831dc4a610325c009c5a10c48fe459e5@finder.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35094"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Jared Finder Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 20 15:08:31 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kqzNu-00091L-RL for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 15:08:30 +0100 Original-Received: from localhost ([::1]:49064 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kqzNt-00008o-Tb for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 09:08:29 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49040) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kqzNG-000891-OD for emacs-devel@gnu.org; Sun, 20 Dec 2020 09:07:51 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:25515) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kqzND-0005cB-R3; Sun, 20 Dec 2020 09:07:49 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id A093180A5C; Sun, 20 Dec 2020 09:07:46 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 235CE80055; Sun, 20 Dec 2020 09:07:45 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1608473265; bh=q9I/E0nNyBDHWbIgHz+Eh+Svx8CqReJ3usq99esOoPU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=aSbLMiv956GHWmGwA3q5UXY+G2fq2TUlXDzBcqtphULMzpaSMl6NzcmtgPJh8v7gv 4oJYkGj1FrYBtxT5b3P5ojGQRWLMV3GYVYUrkAkGvyVwlVwjDi6ef6joC3kLT4KVte dDJyRqUkWmnWE66ojPpWUEvSa/6eO3pHsj7R4qvSLY/EcckoU6zvYSiHQbqWSvZrUZ SBzVC9tqDj1KJxZebSPB5wILH2lFN8fO+jXKiXK4S64uWjfjK0WEiF8T48WfKLCSH7 2+3Ba1xcBBwO5OKOU1a8WeXUuIvN+6nRKxYXmkL64drxLOVnLi1QMujD1ldPZAv+uH tx9Ao1flPJw9g== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id DDB711203CD; Sun, 20 Dec 2020 09:07:44 -0500 (EST) In-Reply-To: <831dc4a610325c009c5a10c48fe459e5@finder.org> (Jared Finder's message of "Sat, 19 Dec 2020 23:26:20 -0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:261327 Archived-At: > I see a few options: > > 1. Change the behavior of the dont-downcase-last parameter to this more > extensive meaning. Update global-set-key (the only other caller who sets > dont-downcase-last in Emacs' code) to take this new behavior > into account. I believe `global-set-key` does want to use this new behavior, yes. > 2. Make the dont-downcase-last parameter have the new behavior only if it is > passed some new value (for example: 'all-fallbacks). Leave the existing > behavior for any other value, especially 'nil and 't. > > 3. [My preference] Like 2, but with a deprecation message on values other > than 'nil, 'all-fallbacks, or 't (or maybe 'downcase-last if we want full > explicitness). This allows maximal ability to define new behaviors in > the future. These sound good as well. I'd even put a deprecation message on the `downcase-last` case. > I like #3 as existing code would run unchanged. The chance that any > existing code passed 'all-fallbacks is extremely low. And anyone supporting > a package outside of Emacs passing some other value will notice the message > when they upgrade to Emacs 28. > > Thoughts? By order of preference, I'd say: #1, then #3 and finally #2. But any one of those 3 is OK for me. Stefan