From: Wolfgang Lux <wolfgang.lux@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: bug#1453: 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 [thread overview]
Message-ID: <3C6EAE70-DE5F-4E2F-AB4C-88B68C8F6AE0@gmail.com> (raw)
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 emacs-pretest-bug@gnu.org
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''
next reply other threads:[~2008-11-29 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 15:25 Wolfgang Lux [this message]
2016-09-10 21:21 ` bug#1453: 23.0.60; Dead keys do not work in dired and similar modes in Cocoa port Alan Third
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=3C6EAE70-DE5F-4E2F-AB4C-88B68C8F6AE0@gmail.com \
--to=wolfgang.lux@gmail.com \
--cc=1453@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
/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.