From: Juanma Barranquero <lekktu@gmail.com>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 9571@debbugs.gnu.org
Subject: bug#9571: 24.0.50; user option to turn off bidi, please
Date: Fri, 23 Sep 2011 13:45:35 +0200 [thread overview]
Message-ID: <CAAeL0SS-vwZ6CWqrLvMXYZY2wvgUD2hALWRV-UH_pmPn7UONJg@mail.gmail.com> (raw)
In-Reply-To: <87d3erfrb5.fsf@gmail.com>
2011/9/23 Štěpán Němec <stepnem@gmail.com>:
> Thank you very much for the explanation. (I guess "pushing bidi down
> everybody's throat" was picturesque in a wrong way, sorry for that; it's
> really just another way of saying "bidi will (one day) become the only
> way to display text in Emacs").
Again: the unicode merge brought the new font backends, which became
the only way to display text in Emacs. That's progress. It's not as if
the previous releases suddenly disappear, for those unable or
unwilling to use newer Emacsen. I switched from Firefox to Chrome
because I cannot bear the new Firefox interface, but I don't expect
the Firefox developers to add ways to make Firefox 6 to behave exactly
like Firefox 4.
> I still think "there is no way back" is all the more reason to be as
> helpful and open about the changes and possible problems as possible.
Pretest *is* the moment to discover, and hopefully fix, the possible problems...
> In
> other words, not clearly saying that bidi might bring problems and how
> to work around them in the user documentation at this point would only
> be reasonable if Emacs bidi was pretty much a solved problem, but that's
> really not the impression I got from the related emacs-devel discussions
> or even from your explanation.
That's a bit absurd, IMO (no offense intended). New features are never
a "solved problem" until they have been extensively tested, and then
some. That has to be done at some point in time. And that moment is
now.
Juanma
next prev parent reply other threads:[~2011-09-23 11:45 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 4:18 bug#9571: 24.0.50; user option to turn off bidi, please Drew Adams
2011-09-22 5:49 ` Eli Zaretskii
2011-09-22 12:31 ` Stefan Monnier
2011-09-22 13:13 ` Drew Adams
2011-09-22 21:44 ` Richard Stallman
2011-09-23 4:13 ` Stefan Monnier
2011-09-23 12:31 ` Richard Stallman
2011-09-23 14:46 ` Eli Zaretskii
2011-09-23 14:55 ` Lars Magne Ingebrigtsen
2011-09-23 15:06 ` Eli Zaretskii
2011-09-23 17:36 ` Stefan Monnier
2011-09-23 18:23 ` Lars Magne Ingebrigtsen
2011-09-23 19:44 ` Richard Stallman
2011-09-23 20:09 ` Eli Zaretskii
2011-09-24 3:56 ` Jason Rumney
2011-09-24 12:28 ` Richard Stallman
2011-09-23 9:13 ` Eli Zaretskii
2011-09-23 12:31 ` Richard Stallman
2011-09-23 14:40 ` Eli Zaretskii
2011-09-23 19:44 ` Richard Stallman
2011-09-23 19:48 ` Eli Zaretskii
2011-09-24 12:28 ` Richard Stallman
2011-09-24 14:04 ` Eli Zaretskii
2011-09-24 17:30 ` Richard Stallman
2011-09-24 19:15 ` Eli Zaretskii
2011-09-24 23:52 ` Richard Stallman
2011-09-23 4:11 ` Stefan Monnier
2011-09-23 8:01 ` Štěpán Němec
2011-09-23 9:21 ` Juanma Barranquero
2011-09-23 10:39 ` Štěpán Němec
2011-09-23 11:01 ` Eli Zaretskii
2011-09-23 16:09 ` Drew Adams
2011-09-23 17:48 ` Eli Zaretskii
2011-09-23 19:03 ` Drew Adams
2011-09-23 19:46 ` Eli Zaretskii
2011-09-23 21:23 ` Drew Adams
2011-09-23 23:21 ` Juanma Barranquero
2011-09-24 0:32 ` Drew Adams
2011-09-24 1:13 ` Juanma Barranquero
2011-09-24 3:46 ` Drew Adams
2011-09-24 8:44 ` Juanma Barranquero
2012-02-22 2:34 ` Glenn Morris
2011-09-24 6:49 ` Eli Zaretskii
2011-09-24 8:46 ` Juanma Barranquero
2011-09-23 20:00 ` Stefan Monnier
2011-09-23 10:18 ` Eli Zaretskii
2011-09-23 11:09 ` Štěpán Němec
2011-09-23 11:45 ` Juanma Barranquero [this message]
2011-09-23 13:01 ` Štěpán Němec
2011-09-23 15:03 ` Eli Zaretskii
2011-09-23 17:46 ` Stefan Monnier
2011-09-23 18:24 ` Eli Zaretskii
2011-09-23 19:10 ` Eli Zaretskii
2011-09-23 11:50 ` Eli Zaretskii
2011-09-24 12:28 ` Richard Stallman
2011-09-24 14:13 ` Eli Zaretskii
2011-09-24 3:53 ` Jason Rumney
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=CAAeL0SS-vwZ6CWqrLvMXYZY2wvgUD2hALWRV-UH_pmPn7UONJg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=9571@debbugs.gnu.org \
--cc=stepnem@gmail.com \
/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.