From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: right-char and left-char
Date: Fri, 07 Oct 2011 14:37:43 +0200 [thread overview]
Message-ID: <83zkhdf04o.fsf@gnu.org> (raw)
In-Reply-To: <7468A6AF024347A3A3E25EC092F18570@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Thu, 6 Oct 2011 15:45:53 -0700
> Cc: emacs-devel@gnu.org
>
> Wrt the _key_ named `left', Eli said:
>
> "Because `left' and `right' behave differently depending on the bidirectional
> context,"...
>
> and "if `left' sometimes moves _forward_ in the buffer, binding it to a command
> called `backward-char' [would be] a lie."
>
> [Of course back then he also said, "[Bidi] _is_ optional: you can set
> bidi-display-reordering to nil" (his emphasis). Now he says that that variable
> is not to make bidi optional for users but is only for bidi debugging. [...]]
Translation: Don't believe a word of what the lying Eli says. Nice.
Of course, back then I also said
The only reason why the bidi-display-reordering flag will stay is
because unibyte buffers should not be reordered.
(which in the meantime is also OBE, since the value of
bidi-display-reordering is ignored in unibyte buffers). I guess
you've conveniently "forgot" to cite that.
How to reconcile this "contradiction" in two sentences I wrote in the
same message, is left as an exercise for the reader.
next prev parent reply other threads:[~2011-10-07 12:37 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 [this message]
2011-10-07 1:49 ` Stefan Monnier
2011-10-07 12:16 ` Eli Zaretskii
2011-10-07 12:04 ` Eli Zaretskii
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=83zkhdf04o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.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.