From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: right-char and left-char
Date: Fri, 07 Oct 2011 14:04:42 +0200 [thread overview]
Message-ID: <838voxgg85.fsf@gnu.org> (raw)
In-Reply-To: <8762k1ojy0.fsf@stupidchicken.com>
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 06 Oct 2011 18:04:55 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The intended behavior is what you see now in Emacs. The manual is
> > correct for the important special case of the paragraph direction that
> > coincides with the text direction. Most L2R text in the world is in
> > L2R paragraphs and most R2L text is in R2L paragraphs, so the
> > description covers most of the use cases.
> >
> > As for the less common use case you mention, yes, the description in
> > the manual could mislead if read too literally; "text is read
> > left-to-right" is intentionally vague to at least not be blatantly
> > wrong.
>
> This lands us in the unfortunate situation where a command named
> `left-char' sometimes moves right, and a command named `right-char'
> sometimes moves left.
That's unfortunate, I agree, but I couldn't find better names.
Suggestions welcome, it's not too late to change these if we want.
> Their names seem to imply that what distinguishes
> these commands from `forward-char'/`backward-char' is their
> directionality.
That isn't _entirely_ false...
next prev parent reply other threads:[~2011-10-07 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 16:45 right-char and left-char Chong Yidong
2011-10-06 18:21 ` Eli Zaretskii
2011-10-06 22:04 ` Chong Yidong
2011-10-06 22:45 ` Drew Adams
2011-10-07 12:37 ` Eli Zaretskii
2011-10-07 1:49 ` Stefan Monnier
2011-10-07 12:16 ` Eli Zaretskii
2011-10-07 12:04 ` Eli Zaretskii [this message]
2011-10-06 22:20 ` Chong Yidong
2011-10-07 12:08 ` Eli Zaretskii
2011-10-07 15:57 ` Chong Yidong
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=838voxgg85.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--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.