From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jim Meyering Newsgroups: gmane.emacs.devel Subject: viper-mode + font-lock-mode malfunction on C continuation line Date: Sat, 16 Oct 2010 15:15:59 +0200 Message-ID: <877hhigtww.fsf@meyering.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1287234989 16433 80.91.229.12 (16 Oct 2010 13:16:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 16 Oct 2010 13:16:29 +0000 (UTC) To: Emacs development discussions Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 16 15:16:27 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P76cP-0001hW-AC for ged-emacs-devel@m.gmane.org; Sat, 16 Oct 2010 15:16:26 +0200 Original-Received: from localhost ([127.0.0.1]:53697 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P76cJ-0005oO-1b for ged-emacs-devel@m.gmane.org; Sat, 16 Oct 2010 09:16:07 -0400 Original-Received: from [140.186.70.92] (port=47880 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P76cD-0005oH-NO for emacs-devel@gnu.org; Sat, 16 Oct 2010 09:16:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P76cC-0006UD-Qh for emacs-devel@gnu.org; Sat, 16 Oct 2010 09:16:01 -0400 Original-Received: from mx.meyering.net ([82.230.74.64]:46590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P76cC-0006Tr-LF for emacs-devel@gnu.org; Sat, 16 Oct 2010 09:16:00 -0400 Original-Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id BEADCE06F; Sat, 16 Oct 2010 15:15:59 +0200 (CEST) Original-Lines: 47 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131760 Archived-At: Hello, I use emacs in viper-mode and font-lock-mode and have been very happy with that set-up for ages. I was surprised to see it malfunction today in a tiny corner case. Here's a minimal test case: printf '#define f(x,s) \\\n' > /tmp/k.c emacs -Q -f viper-mode -f font-lock-mode /tmp/k.c Hit "n" to get past the viper-mode prompt, then "fx" to position the cursor on the "x". Here's the interesting part. The cursor is on the "x" and say you want to change "x,s" to ",": #define f(x,s) \ ^ One way to do that is via "3s", then hit "," and "ESC". That is supposed to leave you with this: #define f(,) \ But it mistakenly produces this: #define f(,x,s) \ That I choose to include "," in the replacement string is critical. Without that, it works fine. It also works fine if you don't use font-lock-mode. This was using the very latest, just built from emacs.git. Here's the most recent commit: commit 8622626c89699b7c756a9359d0c88b5eace76f52 Author: Gnus developers <> Date: Sat Oct 16 01:55:08 2010 +0000 Merge changes made in Gnus trunk. nnimap.el: Use nnheader-message throughout. gnus.el: Autoload gnus-html-show-images. mml.el (mml-generate-mime-1): Add `mml-enable-flow' variable to add a possibility to disable format=flow encoding when using hard newlines. gnus-diary.el (gnus-diary-check-message): Fix gnus-completing-read call. gnus-sum.el (gnus-summary-refer-thread): unconditionally ignore duplicates.