From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: `C-b' is backward-char, `left' is left-char - why?
Date: Thu, 02 Jun 2011 09:23:37 +0200 [thread overview]
Message-ID: <87mxi07l3a.fsf@fencepost.gnu.org> (raw)
In-Reply-To: E1QRlOU-0000vV-Ja@fencepost.gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andy Moreton <andrewjmoreton@gmail.com>
>> Date: Wed, 01 Jun 2011 12:48:15 +0100
>>
>> The help strings for 'left-char and 'backward-char could use some work.
>> It is unclear which moves according to screen display order and which
>> moves according to buffer character order.
>
> I don't feel a need to invest "some work" on the doc string of
> `backward-char', because that function has not changed in ages,
> certainly not now. If its doc string is unclear, then I wonder how
> did we all manage to use it all these years.
>
> Of course, I don't object if someone wants to work on that doc string.
>
> Regarding `left-char' and `right-char', the doc string says:
>
> Depending on the bidirectional context, this may move either
> backward or forward in the buffer.
>
> Believe it or not, but I tried to make it more precise for a long
> time, and this is the best I could come up with.
Correct me if I am wrong, but may it not also _jump_ backward or forward
in the buffer? If I use right-char to move in an L2R context from L2R
text into a short embedded R2L text, I would expect it to move one
position to the right, namely _jump_ to the end of the R2L text, move
backwards over it till it comes to its beginning on the right, then
_jump_ to the following L2R text after its end on the left.
--
David Kastrup
next prev parent reply other threads:[~2011-06-02 7:23 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
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 [this message]
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
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=87mxi07l3a.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 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).