emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1453: closed (23.0.60; Dead keys do not work in dired and similar mo


From: GNU bug Tracking System
Subject: bug#1453: closed (23.0.60; Dead keys do not work in dired and similar modes in Cocoa port)
Date: Sun, 22 Dec 2019 11:57:01 +0000

Your message dated Sun, 22 Dec 2019 11:56:17 +0000
with message-id <address@hidden>
and subject line Re: bug#1453: 23.0.60; Dead keys do not work in dired and 
similar modes in Cocoa port
has caused the debbugs.gnu.org bug report #1453,
regarding 23.0.60; Dead keys do not work in dired and similar modes in Cocoa 
port
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
1453: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1453
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.60; Dead keys do not work in dired and similar modes in Cocoa port Date: Sat, 29 Nov 2008 16:25:34 +0100
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the address@hidden mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

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: #<buffer ~>" followed by an error
message "Wrong type argument: overlayp, nil" upon the next event.

In an attempt to fix this issue with some other Emacs version, I have added
the lines
  (define-key function-key-map [dead-tilde] "~")
  (put 'dead-tilde 'ascii-character ?~)
to .emacs, but these do not help (nor does removing them from .emacs).

Note that with a German keyboard layout, Alt-n is the only way to enter a
tilde character. The ASCII tilde is not bound to any key. (Actually, one
could enter ASCII tilde via key combinations Ctrl-Alt-n and Command- Alt-n,
respectively, but obviously this does not work for Emacs.)

In GNU Emacs 23.0.60.1 (powerpc-apple-darwin8.11.0, NS apple- appkit-824.48)
 of 2008-11-21 on Onyx.local
Windowing system distributor `Apple', version 97.112.112.108.101.45.97.112.112.107.105.116.45.56.50.52.46.52.56
configured using `configure  '--with-ns''




--- End Message ---
--- Begin Message --- Subject: Re: 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 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (darwin)
Alan Third <address@hidden> writes:

> Wolfgang Lux <address@hidden> 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: #<buffer ~>" 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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]