From: Eli Zaretskii <eliz@gnu.org>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 9571@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#9571: 24.0.50; user option to turn off bidi, please
Date: Fri, 23 Sep 2011 18:03:16 +0300 [thread overview]
Message-ID: <83r537qp1n.fsf@gnu.org> (raw)
In-Reply-To: <878vpffm4z.fsf@gmail.com>
> From: Štěpán Němec <stepnem@gmail.com>
> Cc: 9571@debbugs.gnu.org
> Date: Fri, 23 Sep 2011 15:01:32 +0200
>
> > I happen to be a documentation freak, and tried to do my best in
> > documenting everything related to bidi. If you can suggest specific
> > changes to the user manual or NEWS about this, please do. Saying in
> > the manual that some feature "means trouble" is not something we use
> > to do, because users will say "if it's trouble, why don't you fix
> > it?". We need to find a way of saying something useful that will help
> > users nonetheless. Suggestions are welcome.
>
> When you take one example Lars reported recently -- a buffer where the
> current bidi code wasn't able to diagnose the paragraph direction
> properly (or something) in a relatively untypical buffer (a lot of long
> lines without paragraph breaks). It made the buffer unusable. Now, how
> would a user diagnose or solve this issue? How would the current
> documentation help him in doing so?
Documentation cannot help with this, because it was a bug. It
happened in a situation that I never envisioned, and that took several
months to bump into, since bidi-display-reordering was turned on. The
bug was fixed since then.
I expect users who bump into such issues, and cannot find anything to
help them in the manual, to ask for help on help-gnu-emacs or on
emacs-devel. Then they will be provided with workarounds if they are
available, or with patches if not. IOW, treat that as we always do
with bugs.
I also expect such issues to be extremely rare and marginal by the end
of the pretest, provided that people report the problems.
> I think unless you're pretty sure such problems are not likely to occur
> again, you should at least say (in NEWS if not in the manual; I would
> probably check the NEWS first in such situation anyway) that such things
> can happen and how to work around it
I wouldn't know what to say in a way that will be useful. Bugs that
are reported are being fixed fairly quickly, so describing them would
be an exercise in futility. Bugs that were not yet reported are
unknown and cannot be described. The assumption that every single
slowdown and every display-related bug in Emacs 24 are due to the
bidirectional display engine is profoundly false, at least lately, so
saying "as soon as you see any problem whatsoever, turn off bidi"
would be crying wolf for no good reason.
IOW, I feel that the issue is blown out of proportions for reason I
cannot understand. By and large, THERE IS NO PROBLEM. Fear of
problems, maybe. But no real problems, at least not reported ones.
next prev parent reply other threads:[~2011-09-23 15:03 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
2011-09-23 13:01 ` Štěpán Němec
2011-09-23 15:03 ` Eli Zaretskii [this message]
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
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=83r537qp1n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9571@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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 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).