From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alan Third Newsgroups: gmane.emacs.bugs Subject: bug#1453: 23.0.60; Dead keys do not work in dired and similar modes in Cocoa port Date: Sun, 22 Dec 2019 11:56:17 +0000 Message-ID: References: <3C6EAE70-DE5F-4E2F-AB4C-88B68C8F6AE0@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="3160"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (darwin) Cc: 1453-done@debbugs.gnu.org To: Wolfgang Lux Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Dec 22 13:03:41 2019 Return-path: Envelope-to: geb-bug-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 1iizxV-0000j4-40 for geb-bug-gnu-emacs@m.gmane.org; Sun, 22 Dec 2019 13:03:41 +0100 Original-Received: from localhost ([::1]:47132 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iizxT-0004a9-R0 for geb-bug-gnu-emacs@m.gmane.org; Sun, 22 Dec 2019 07:03:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36661) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iizr5-0005sS-IX for bug-gnu-emacs@gnu.org; Sun, 22 Dec 2019 06:57:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iizr4-0001v0-9d for bug-gnu-emacs@gnu.org; Sun, 22 Dec 2019 06:57:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43157) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iizr4-0001tO-0O for bug-gnu-emacs@gnu.org; Sun, 22 Dec 2019 06:57:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iizr3-0000A4-TC for bug-gnu-emacs@gnu.org; Sun, 22 Dec 2019 06:57:01 -0500 Resent-From: Alan Third Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Sun, 22 Dec 2019 11:57:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 1453 X-GNU-PR-Package: emacs Mail-Followup-To: 1453@debbugs.gnu.org, alan@idiocy.org, wolfgang.lux@gmail.com Original-Received: via spool by 1453-done@debbugs.gnu.org id=D1453.1577015786559 (code D ref 1453); Sun, 22 Dec 2019 11:57:01 +0000 Original-Received: (at 1453-done) by debbugs.gnu.org; 22 Dec 2019 11:56:26 +0000 Original-Received: from localhost ([127.0.0.1]:49130 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iizqU-00008x-Ez for submit@debbugs.gnu.org; Sun, 22 Dec 2019 06:56:26 -0500 Original-Received: from mail-wr1-f49.google.com ([209.85.221.49]:46541) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iizqS-00008h-VJ for 1453-done@debbugs.gnu.org; Sun, 22 Dec 2019 06:56:25 -0500 Original-Received: by mail-wr1-f49.google.com with SMTP id z7so13703125wrl.13 for <1453-done@debbugs.gnu.org>; Sun, 22 Dec 2019 03:56:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=8zwsuQ1dgKRreZsxU2AcZ9zYkqoIOWILlMuKxJE+xGI=; b=BfLhhBb/MdYsDFjknwHsxBRH81f2A8gtLPfHQMtsKPn62Ql9wcrbTBhLeUo/anI4si 3PDDjHBiNimlnP5ThY2D/4p+0UwSN4tRAXaNwMGPCW5edKUutT7C2VQopxD9ldeVuuDj heksOop91UV0KmN2hXg8Nt2es070TxlkzOLLkOPRBN/EPvrDo8LitxxJM638VAZhFspU kvVbQhGm48zWN4uhcW5Y93KqT/ldzYSzBPoGcF6qG8LtukXJb5ufjau1vsJ+UY9GYC4h Zlie6aSQLbMp+dmiAq7jlq2KxHbI+6bSL1eGdfIC6sJLf+YWjQTYUt/FDLZDqVCpZF4Y oPQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=8zwsuQ1dgKRreZsxU2AcZ9zYkqoIOWILlMuKxJE+xGI=; b=B3aO9BboGn0RphkiLKI4WT4WIe+8IOCxrJkyUs+afbSj/eLh0+yJ5rDQ3jrAB0DGNp n4kEyONRvi3UjolxSM8NdF3LyQYaJNjMiVU4n+q5iWfysd413iurevKrxxqLQ5/7I6qI MM0dFwx6Q6lBuF16KKKDoTfeojZV+m3U5PGy+F4ctOEcD1aVOD8nXCMeWWVl4s14dFMF 7kPIu8llt3yzOHRubkp2TEXq9OFCsYWKVBPzfgzNibNUMwVmftYyIaSfj9AqkAa6sKUK ll/GufQMDpE0EO/X54/o5zYe2dWNUaeA7G7mWROPKZeaqELXYJSSIMpditOyFRywf2jQ garA== X-Gm-Message-State: APjAAAVvHy79+qtCKe0330sR0Gg+AbzWNOR7a3QD1AZELlZMyOr74F6v v4kqBmuuucVnSS5UeAdq0PzUMozsCS+wHA== X-Google-Smtp-Source: APXvYqybVkXOrxTbZBWwJ5GRM5Uu4PV/pkwsZ1KWj+kpahzy+KFAgASBBGfSGycD4kpg50fzG33ipQ== X-Received: by 2002:a5d:6a0f:: with SMTP id m15mr25072455wru.40.1577015778800; Sun, 22 Dec 2019 03:56:18 -0800 (PST) Original-Received: from breton.holly.idiocy.org (ip6-2001-08b0-03f8-8129-488a-38f7-f32f-09bb.holly.idiocy.org. [2001:8b0:3f8:8129:488a:38f7:f32f:9bb]) by smtp.gmail.com with ESMTPSA id h66sm18214326wme.41.2019.12.22.03.56.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 Dec 2019 03:56:17 -0800 (PST) In-Reply-To: (Alan Third's message of "Sat, 10 Sep 2016 22:21:34 +0100") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:173634 Archived-At: Alan Third writes: > Wolfgang Lux writes: > >> Dired mode binds ~ to dired-flag-backup-files. When one attempts >> entering >> ~ via the dead-key combination Alt-n (assuming the Alt key is not used >> as >> a modifier key and Command is interpreted as Meta key), Emacs first >> reports >> an error message "Buffer is read-only: #" followed by an error >> message "Wrong type argument: overlayp, nil" upon the next event. > > This is still sort of an issue in Emacs 25. As far as I can tell Emacs > still gives the "buffer is read-only" message, but as soon as another > key is hit actually executes dired-flag-backup-files. > > I also suspect this won't be limited to the NS port, but will be an > issue anywhere you can use dead-keys in a read-only buffer. > > I can't think of any reason to try and display the partially complete > input when the buffer's read-only, but I can't see where this dead-key > entry code is located to see if it's possible to do a check. The fix for bug#23412 fixes this. It inserts the working text into the buffer so you can see what's being typed, but once it completes it deletes it and dired takes its action. It maybe looks a little weird, but it works and I'm not sure what else we would do other than just not display the working text at all. -- Alan Third