From: Juri Linkov <juri@jurta.org>
To: emacs-devel@gnu.org
Subject: Re: C-n and C-a
Date: Fri, 30 Jan 2009 02:32:29 +0200 [thread overview]
Message-ID: <87skn1fxaw.fsf@jurta.org> (raw)
In-Reply-To: <87bptqywpq.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 29 Jan 2009 16:10:25 +0100")
>> The new definitions of C-n and C-p seem to work reasonably
>> conveniently with the very long lines that non-Emacs-users often
>> write. However, it is very counterintuitive that C-a and C-e have not
>> been changed in the same way.
>
> I mentioned this inconsistencies before in
> <874p55z20j.fsf@thinkpad.tsdh.de>. I was told that the current behavior
> was due to a consensus. But still I don't like it, so I switch on
> `visual-line-mode' where everything operates consistently on screen
> lines.
In addition to inconsistencies and lack of convenient key bindings
there are also problems with the used terminology. There are
two similar confusing names:
line-move-visual
visual-line-mode
The former defines half-real/half-screen line motion mode,
and the latter has a name that says nothing to most users.
I think if we want to achieve simplicity and intuitiveness
then we should have a mode
word-wrap-mode
with a pair of variables to define variations for key bindings
and visual appearance.
By default, `word-wrap-mode' could bind C-n/C-p and C-a/C-e to
visual line motion commands, and also provide alternative keys
for real line motion commands when `line-move-visual' is non-nil.
But the nil value of `line-move-visual' could reverse the meaning
of these key bindings.
Another variant is to define a mode
line-wrap-mode
with C-n/C-p and C-a/C-e bound to visual line motion commands and
`line-move-visual' behaving as described above. And additionally
it could provide a variable `word-wrap' to define wrapping boundaries
(word vs non-word).
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-01-30 0:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:32 C-n and C-a Richard M Stallman
2009-01-29 15:10 ` Tassilo Horn
2009-01-29 16:09 ` Harald Hanche-Olsen
2009-01-29 17:15 ` Tassilo Horn
2009-01-29 19:40 ` Adrian Robert
2009-01-30 0:32 ` Juri Linkov [this message]
2009-01-30 1:20 ` Stefan Monnier
2009-01-30 9:45 ` Eli Zaretskii
2009-01-31 17:45 ` Juri Linkov
2009-01-31 19:47 ` Stefan Monnier
2009-02-02 1:45 ` Juri Linkov
2009-01-31 20:33 ` Chong Yidong
2009-02-02 1:47 ` Juri Linkov
2009-01-30 7:25 ` Richard M Stallman
2009-01-29 18:24 ` Karl Fogel
2009-01-29 18:48 ` Harald Hanche-Olsen
2009-01-29 21:41 ` Stefan Monnier
2009-01-30 16:07 ` Sascha Wilde
2009-01-31 20:34 ` Chong Yidong
2009-01-30 0:29 ` Juri Linkov
2009-01-30 6:12 ` mail
2009-01-31 17:45 ` Juri Linkov
2009-01-31 22:35 ` Drew Adams
2009-02-01 20:11 ` Leo
2009-02-03 15:11 ` Carsten Dominik
2009-02-02 1:54 ` Juri Linkov
2009-02-02 2:25 ` Drew Adams
2009-02-02 9:45 ` Juri Linkov
2009-02-06 0:45 ` Juri Linkov
2009-02-06 16:04 ` Chong Yidong
2009-02-08 0:48 ` Juri Linkov
2009-02-08 20:08 ` Stefan Monnier
2009-02-09 21:22 ` Christian Schlauer
2009-02-09 22:02 ` Drew Adams
2009-02-10 2:05 ` Stefan Monnier
2009-02-10 3:11 ` Drew Adams
2009-02-11 22:45 ` Juri Linkov
2009-02-12 2:01 ` Miles Bader
2009-02-12 10:05 ` Juri Linkov
2009-02-12 11:04 ` Miles Bader
2009-02-13 6:33 ` Richard M Stallman
2009-02-07 1:52 ` Stefan Monnier
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=87skn1fxaw.fsf@jurta.org \
--to=juri@jurta.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).