From: Alan Third <alan@idiocy.org>
To: Wolfgang Lux <wolfgang.lux@gmail.com>
Cc: 1453@debbugs.gnu.org
Subject: bug#1453: 23.0.60; Dead keys do not work in dired and similar modes in Cocoa port
Date: Sat, 10 Sep 2016 22:21:34 +0100 [thread overview]
Message-ID: <m21t0r78o1.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <3C6EAE70-DE5F-4E2F-AB4C-88B68C8F6AE0@gmail.com> (Wolfgang Lux's message of "Sat, 29 Nov 2008 16:25:34 +0100")
Wolfgang Lux <wolfgang.lux@gmail.com> 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.
--
Alan Third
next prev parent reply other threads:[~2016-09-10 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 15:25 bug#1453: 23.0.60; Dead keys do not work in dired and similar modes in Cocoa port Wolfgang Lux
2016-09-10 21:21 ` Alan Third [this message]
2019-12-22 11:56 ` Alan Third
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21t0r78o1.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=1453@debbugs.gnu.org \
--cc=wolfgang.lux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.