From: David Reitter <david.reitter@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 1236@emacsbugs.donarmstrong.com
Subject: bug#1236: ispell-complete-word / key binding not shown in menu
Date: Sat, 25 Oct 2008 17:27:37 -0400 [thread overview]
Message-ID: <EE5D4DAD-109F-4DFC-A6F6-3A71B166421E@gmail.com> (raw)
In-Reply-To: <krzlksldi7.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
On 25 Oct 2008, at 14:45, Glenn Morris wrote:
> YAMAMOTO Mitsuharu wrote:
>
>> Probably you tried with Emacs 23, and Emacs 22 on GNU/Linux would
>> behave as OP described.
>
> I did indeed, since Emacs 22 is dead, and the problem was also said to
> occur with "a recent build of Cocoa (23)". Does it? (I can't build
> that.)
In general: given that there are tens if not hundreds of thousands of
users out there on Emacs 22, with stopping to fix bugs we're not doing
ourselves a favor.
Applying Stefan's patch (which just turns off this cache) causes a
crash while building (before dumping), which I don't have the chance
to investigate further.
Indeed, the key hint problem occurred with 23 as well, so perhaps we
should fix it on that end first.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]
next prev parent reply other threads:[~2008-10-25 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18945223.post@talk.nabble.com>
2008-10-24 2:31 ` bug#1236: ispell-complete-word / key binding not shown in menu David Reitter
2008-10-24 4:18 ` Glenn Morris
2008-10-24 4:30 ` Processed: " Emacs bug Tracking System
2008-10-25 8:37 ` YAMAMOTO Mitsuharu
2008-10-25 18:45 ` Glenn Morris
2008-10-25 21:27 ` David Reitter [this message]
2008-10-26 4:18 ` YAMAMOTO Mitsuharu
2008-10-26 13:56 ` David Reitter
2009-01-22 12:35 ` bug#1236: marked as done (ispell-complete-word / key binding not shown in menu) Emacs bug Tracking System
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=EE5D4DAD-109F-4DFC-A6F6-3A71B166421E@gmail.com \
--to=david.reitter@gmail.com \
--cc=1236@emacsbugs.donarmstrong.com \
--cc=rgm@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.