From: Jim Meyering <jim@meyering.net>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: viper-mode + font-lock-mode malfunction on C continuation line
Date: Sat, 16 Oct 2010 15:15:59 +0200 [thread overview]
Message-ID: <877hhigtww.fsf@meyering.net> (raw)
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.
reply other threads:[~2010-10-16 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877hhigtww.fsf@meyering.net \
--to=jim@meyering.net \
--cc=emacs-devel@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.