From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.bugs Subject: Re: flyspell interferes with C-c C-c (mail mode, vc-log-mode, etc) Date: Tue, 19 Nov 2002 03:48:32 -0500 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1037695672 8201 80.91.224.249 (19 Nov 2002 08:47:52 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 19 Nov 2002 08:47:52 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18E42x-000281-00 for ; Tue, 19 Nov 2002 09:47:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 18E44O-0001To-00; Tue, 19 Nov 2002 03:49:20 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 18E43g-0001CY-00 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2002 03:48:36 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 18E43d-00017v-00 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2002 03:48:36 -0500 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.10) id 18E43d-00017L-00 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2002 03:48:33 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.10) id 18E43c-0004nT-00; Tue, 19 Nov 2002 03:48:32 -0500 Original-To: era@iki.fi In-reply-to: (message from era eriksson on Mon, 18 Nov 2002 09:22:33 +0200) Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:3906 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:3906 Could you possibly provide one completely specific test case rather than leaving some aspects unspecified? Show us the text to use, say precisely which mode to use, etc. That is the most reliable way to enable us to see the problem. The Bugs section in the Emacs manual provides guidelines on this.