From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: viper-mode: "r <Return>" does not work as expected
Date: Thu, 28 Apr 2005 12:44:55 -0600 [thread overview]
Message-ID: <d4rakp$k9t$1@sea.gmane.org> (raw)
In-Reply-To: <d4q3ib$1s7$1@wsc10.lrz-muenchen.de>
Olaf Dietrich wrote:
> I tried this in all viper-mode levels (GNU Emacs 21.4.1, i386 Linux):
>
> Inserting a new line break in an existing line by "r <Return>"
> (more exactly: replacing the current character by a newline)
> does not work; instead, '^M' appears as replacement text.
>
> (The alternative "r C-j" _does_ work, but is not what my fingers
> are used to do in vi.)
>
> Is it possible to make "r <Return>" work as well? Is this a known
> limitation or bug? (Well, yes, it is known, I found the post
>
> From: eesti@corp.earthlink.net
> Subject: Emacs VIPER mode: RETURN shows up as ^M after replace
> Newsgroups: gnu.emacs.help
> Message-ID: <%NFK8.379$se.11@newsread1.prod.itd.earthlink.net>
> Date: Mon, 03 Jun 2002 08:29:47 GMT
>
> but I haven't found any suggestions how to change this behavior.)
The version of viper-cmd.el distributed with Emacs 21.3 has this snippet
in the viper-replace-char-subr function:
(if (eq char ?\C-m) (setq char ?\n))
So perhaps you're using an old version of viper -- what do `M-x
locate-library RET viper' and `M-x list-load-path-shadows' tell
you?
--
Kevin Rodgers
next prev parent reply other threads:[~2005-04-28 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4861u$28v$1@wsc10.lrz-muenchen.de>
2005-04-28 7:32 ` viper-mode: "r <Return>" does not work as expected Olaf Dietrich
2005-04-28 18:44 ` Kevin Rodgers [this message]
[not found] ` <mailman.3342.1114714165.2895.help-gnu-emacs@gnu.org>
2005-04-29 7:28 ` Olaf Dietrich
2005-04-29 12:34 ` Olaf Dietrich
2005-04-29 18:55 ` Kevin Rodgers
2005-05-06 7:27 ` Olaf Dietrich
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='d4rakp$k9t$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).