From: odt@dtrx.de (Olaf Dietrich)
Subject: Re: viper-mode: "r <Return>" does not work as expected
Date: 29 Apr 2005 07:28:10 GMT [thread overview]
Message-ID: <d4snma$at3$1@wsc10.lrz-muenchen.de> (raw)
In-Reply-To: mailman.3342.1114714165.2895.help-gnu-emacs@gnu.org
Kevin Rodgers <ihs_4664@yahoo.com>:
> Olaf Dietrich wrote:
>>
>> 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.)
>
> 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))
This line is in my viper-cmd.el as well:
| (defun viper-replace-char-subr (com arg)
| (let ((inhibit-quit t)
| char)
| (viper-set-complex-command-for-undo)
| (or (eq viper-intermediate-command 'viper-repeat)
| (viper-special-read-and-insert-char))
|
| (if (eq char ?\C-m) (setq char ?\n))
...
viper.el says:
| (defconst viper-version "3.11.1 of September 9, 2001"
| "The current version of Viper")
> So perhaps you're using an old version of viper --
> what do `M-x locate-library RET viper'
| Library is file ..../emacs/21.4/lisp/emulation/viper.elc
(The path appears correct.)
> and `M-x list-load-path-shadows' tell you?
| No Emacs Lisp load-path shadowings were found
Does this make any sense?
Thanks,
Olaf
next prev parent reply other threads:[~2005-04-29 7:28 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
[not found] ` <mailman.3342.1114714165.2895.help-gnu-emacs@gnu.org>
2005-04-29 7:28 ` Olaf Dietrich [this message]
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='d4snma$at3$1@wsc10.lrz-muenchen.de' \
--to=odt@dtrx.de \
/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).