From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.comp.lib.ncurses.bugs,gmane.emacs.devel Subject: Re: Emacs difficulties in linux console with ncurses-6.3 caused by kcbt=\E^I. Date: Sat, 7 May 2022 17:37:10 +0000 Message-ID: References: <20220506000102.GA10144@prl-debianold-64.jexium-island.net> <83v8uizd6r.fsf@gnu.org> <83y1zdy61z.fsf@gnu.org> <83levdxu3y.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36476"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dickey@his.com, bug-ncurses@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: bug-ncurses-bounces+gnu-bug-ncurses=m.gmane-mx.org@gnu.org Sat May 07 19:37:47 2022 Return-path: Envelope-to: gnu-bug-ncurses@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 1nnONE-0009E5-AR for gnu-bug-ncurses@m.gmane-mx.org; Sat, 07 May 2022 19:37:44 +0200 Original-Received: from localhost ([::1]:58866 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nnOND-0006zj-4s for gnu-bug-ncurses@m.gmane-mx.org; Sat, 07 May 2022 13:37:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47042) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nnOMm-0006yM-Ls for bug-ncurses@gnu.org; Sat, 07 May 2022 13:37:16 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:36917 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1nnOMj-0007EA-Ju for bug-ncurses@gnu.org; Sat, 07 May 2022 13:37:15 -0400 Original-Received: (qmail 72171 invoked by uid 3782); 7 May 2022 17:37:11 -0000 Original-Received: from acm.muc.de (p2e5d55ed.dip0.t-ipconnect.de [46.93.85.237]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 07 May 2022 19:37:11 +0200 Original-Received: (qmail 3466 invoked by uid 1000); 7 May 2022 17:37:10 -0000 Content-Disposition: inline In-Reply-To: <83levdxu3y.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: bug-ncurses@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Bug reports for ncurses, the GNU implementation of curses" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-ncurses-bounces+gnu-bug-ncurses=m.gmane-mx.org@gnu.org Original-Sender: "Bug-ncurses" Xref: news.gmane.io gmane.comp.lib.ncurses.bugs:8550 gmane.emacs.devel:289419 Archived-At: Hello, Eli. On Sat, May 07, 2022 at 18:03:45 +0300, Eli Zaretskii wrote: > > Date: Sat, 7 May 2022 14:35:06 +0000 > > Cc: dickey@his.com, bug-ncurses@gnu.org, emacs-devel@gnu.org > > From: Alan Mackenzie > > > > Maybe we can write an entry in PROBLEMS and leave it to the user to fix > > > > in her .emacs. Or maybe we can put code in lisp/term/linux.el > > > > ourselves. > > > I'm okay with both alternatives, since I have no opinion on what is > > > more important to users of Emacs on the Linux console. > > Having thought about it, I think putting > > (define-key input-decode-map "\e\t" nil) > > into lisp/term/linux.el would be the best thing. It will restore Emacs > > on the Linux console to what it was before the recent ncurses release. > Fine with me. OK, DONE, it works. :-) > > > > I don't know how typical I am of Linux console users, but I have my > > > > keymap set up to send a different code for - namely > > > > "\033[4}\011". > > > Perhaps that PROBLEMS entry could suggest that as well, so that users > > > could have the cake and eat it, too. > > Here's a first stab at the PROBLEMS entry, under * Runtime problems on > > character terminals>: > Also fine, thanks. But please capitalize "TAB" and "ESC" in the text, > to make them consistent with our notation elsewhere. One other little thing: I think this problem counts as "major" or "safe", so the fix should go onto the release branch, shouldn't it, despite the upcoming release being nn.2? -- Alan Mackenzie (Nuremberg, Germany).