From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Ctrl-[ ? Date: Sat, 08 Jun 2019 23:09:05 +0300 Message-ID: <83imtfdela.fsf@gnu.org> References: <83lfydrkde.fsf@gnu.org> <874l51q0s4.fsf@telefonica.net> <83ef45rdij.fsf@gnu.org> <87zhmto6fa.fsf@telefonica.net> <20190607163017.GA32029@tuxteam.de> <96B116FC-8007-4C42-9AE6-585530D0C76E@comcast.net> <87muisor2h.fsf@telefonica.net> <20190608084404.GB28228@tuxteam.de> <87h890ns41.fsf@telefonica.net> <83pnnonr15.fsf@gnu.org> <20190608135853.GA4323@tuxteam.de> <87d0jnooh4.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="160595"; mail-complaints-to="usenet@blaine.gmane.org" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 08 22:09:31 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hZhed-000feE-34 for geh-help-gnu-emacs@m.gmane.org; Sat, 08 Jun 2019 22:09:31 +0200 Original-Received: from localhost ([::1]:60340 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hZheb-0003L1-FB for geh-help-gnu-emacs@m.gmane.org; Sat, 08 Jun 2019 16:09:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48235) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hZheN-0003Kq-Cc for help-gnu-emacs@gnu.org; Sat, 08 Jun 2019 16:09:17 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47532) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hZheM-0003j1-7Z for help-gnu-emacs@gnu.org; Sat, 08 Jun 2019 16:09:14 -0400 Original-Received: from [176.228.60.248] (port=2543 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hZheL-0002B8-LA for help-gnu-emacs@gnu.org; Sat, 08 Jun 2019 16:09:14 -0400 In-reply-to: <87d0jnooh4.fsf@telefonica.net> (message from =?utf-8?Q?=C3=93scar?= Fuentes on Sat, 08 Jun 2019 21:40:07 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120844 Archived-At: > From: Óscar Fuentes > Date: Sat, 08 Jun 2019 21:40:07 +0200 > > No, I don't know enough. I just looked at keyboard.c for several minutes > and can only understand your cautions about touching what it seems a > pile of bugfixes on top of a stack of hacks to deal with quirky > terminals shoehorning new paradigms like guis into a pre-existing > tty-based design. That's a myth not really backed up by the code. > Oh, and the interactions with the display engine, as if handling > terminals were not complex enough on itself. Another myth. > >> ... Suffices it to say that several times during the recent years > >> when we needed to make seemingly-simple changes and fixes in that > >> code, no one had the courage to approve such changes. > > I'm sure that that is not Eli's intention, but encouraging it is not. It's how things are. Whether they are encouraging or not depends on what you intend to do about that. If you want to change/improve it, come aboard, study the code and its callers, and then redesign and reimplement it. Seriously, what did you expect from a 35-year old program that gives its users an unprecedented amount of power to tweak its workings? You can call terminals "quirky" all you want, but they are all still very much with us, and we must support them, the newer ones, the mouse, you name it -- all in the same event queue, because that's how Lisp programs expect to see the input events.