From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: `C-b' is backward-char, `left' is left-char - why?
Date: Fri, 03 Jun 2011 22:56:53 +0200 [thread overview]
Message-ID: <87sjrq3a7e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 83ipsmeu88.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> The idea is that <left> moves forward when the paragraph direction is
> L2R, and <right> moves forward in R2L paragraphs. But they both move
> in the reading (a.k.a. "logical") order, which in Emacs means in the
> direction of increasing character positions. Moving in strict visual
> order (i.e. always left or right on the screen) is also possible, but
> less desirable, because that's not the order in which people read the
> text.
Left/Right are for positioning the cursor. They have nothing to do with
the order people read the text in. I don't want my mouse to change
direction on RL text.
> But what you suggest is neither visual nor logical order,
Huh? I suggest visual order. Period.
> so it seems to be the worst of both worlds.
I have no idea what you are imagining here.
> I, for one, have trouble predicting where I will wind up, and need to
> think carefully before I give the right answer. That's not a good UI,
> IMO.
Press left, end up at the next position to the left. Press right, end
up at the next position to the right. No need to even recognize whether
the glyphs at question are R2L or L2R: the effect is immediately
obvious. Without thinking, without even knowing anything about the
R2L/L2R properties of the glyphs. forward-character and
backward-character require more thinking.
--
David Kastrup
next prev parent reply other threads:[~2011-06-03 20:56 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 20:40 `C-b' is backward-char, `left' is left-char - why? Drew Adams
2011-05-27 20:48 ` Pascal J. Bourguignon
2011-05-27 21:11 ` Eli Zaretskii
2011-05-27 22:08 ` Drew Adams
2011-05-28 0:19 ` Nix
2011-05-27 21:09 ` Eli Zaretskii
2011-05-27 21:13 ` Eli Zaretskii
2011-05-27 22:08 ` Drew Adams
2011-05-27 22:23 ` Antoine Levitt
2011-05-27 23:19 ` Drew Adams
2011-05-28 0:46 ` Mohsen BANAN
2011-05-28 1:53 ` Drew Adams
2011-05-28 2:24 ` Mohsen BANAN
2011-05-28 8:00 ` Eli Zaretskii
2011-05-27 23:09 ` PJ Weisberg
2011-05-27 23:23 ` Drew Adams
2011-05-28 0:25 ` PJ Weisberg
2011-05-28 0:39 ` Drew Adams
2011-05-28 6:57 ` David Kastrup
2011-05-28 8:21 ` Eli Zaretskii
2011-05-28 0:48 ` Stefan Monnier
2011-05-28 1:54 ` Drew Adams
2011-05-28 7:07 ` David Kastrup
2011-05-28 8:26 ` Eli Zaretskii
2011-05-30 3:57 ` Stefan Monnier
2011-05-31 14:18 ` Davis Herring
2011-05-31 14:39 ` Eli Zaretskii
2011-06-01 11:48 ` Andy Moreton
2011-06-01 13:23 ` Eli Zaretskii
2011-06-01 23:26 ` Andy Moreton
2011-06-02 4:37 ` Eli Zaretskii
2011-06-02 10:38 ` Andy Moreton
2011-06-02 11:12 ` Eli Zaretskii
2011-06-02 12:59 ` Andy Moreton
2011-06-02 15:09 ` Eli Zaretskii
2011-06-02 16:23 ` Andy Moreton
2011-06-02 17:43 ` Eli Zaretskii
2011-06-02 21:42 ` Andy Moreton
2011-06-03 7:01 ` Eli Zaretskii
2011-06-02 17:09 ` David Kastrup
2011-06-02 18:05 ` Eli Zaretskii
2011-06-03 14:35 ` David Kastrup
2011-06-03 15:08 ` Eli Zaretskii
2011-06-03 15:14 ` David Kastrup
2011-06-03 16:48 ` Eli Zaretskii
2011-06-03 20:56 ` David Kastrup [this message]
2011-06-04 6:28 ` Eli Zaretskii
2011-06-05 16:51 ` Ehud Karni
2011-06-05 17:10 ` Eli Zaretskii
2011-06-05 17:19 ` Ehud Karni
2011-06-05 17:26 ` David Kastrup
2011-06-05 17:44 ` Eli Zaretskii
2011-06-05 18:26 ` David Kastrup
2011-06-05 19:22 ` Eli Zaretskii
2011-06-07 8:51 ` David Kastrup
2011-06-07 10:54 ` Eli Zaretskii
2011-06-02 15:35 ` PJ Weisberg
2011-06-02 17:44 ` Eli Zaretskii
2011-06-02 19:29 ` PJ Weisberg
2011-06-02 21:10 ` Eli Zaretskii
2011-06-03 0:47 ` Kenichi Handa
2011-06-03 7:13 ` Eli Zaretskii
2011-06-05 11:27 ` Kenichi Handa
2011-06-05 13:04 ` Eli Zaretskii
2011-06-02 7:23 ` David Kastrup
2011-06-02 8:59 ` Eli Zaretskii
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=87sjrq3a7e.fsf@fencepost.gnu.org \
--to=dak@gnu.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 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.