From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Brubeck Unhammer <unhammer@fsfe.org>
Cc: 44329@debbugs.gnu.org
Subject: bug#44329: 28.0.50; Crash in bidi_mirror_char on view-hello-file when no bidi-display-reordering (harfbuzz)
Date: Fri, 30 Oct 2020 23:01:03 +0200 [thread overview]
Message-ID: <83361va0og.fsf@gnu.org> (raw)
In-Reply-To: <87h7qbqwca.fsf@fastmail.com> (message from Kevin Brubeck Unhammer on Fri, 30 Oct 2020 21:42:45 +0100)
> From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
> Cc: 44329@debbugs.gnu.org
> Date: Fri, 30 Oct 2020 21:42:45 +0100
>
> > This isn't supported: that variable is not supposed to be set nil,
> > except for debugging display problems.
>
> Is there something like make-obsolete-variable for this case that would
> give a warning in init.el on this variable?
The doc string already does warn. The variable is not obsolete, it is
useful for debugging the display code.
> I am not the only one setting it to nil
> https://github.com/search?q=setq+bidi-display-reordering+nil&type=code
> https://emacs.stackexchange.com/a/21761/730 :) so a warning might stop
> some other poor user from wasting half a day on a pointless debugging
> mission.
I make a point of warning against that every time I see such advice,
but my abilities are limited.
> (The manual also mentions the variable's effect without saying you
> shouldn't set it
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Bidirectional-Editing.html
You assume people who do this read the manual...
next prev parent reply other threads:[~2020-10-30 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 14:56 bug#44329: 28.0.50; Crash in bidi_mirror_char on view-hello-file when no bidi-display-reordering (harfbuzz) Kevin Brubeck Unhammer
2020-10-30 15:42 ` Eli Zaretskii
2020-10-30 16:04 ` Stefan Kangas
2020-10-30 20:42 ` Kevin Brubeck Unhammer
2020-10-30 21:01 ` Eli Zaretskii [this message]
2020-10-30 23:29 ` Stefan Kangas
2020-10-31 7:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83361va0og.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44329@debbugs.gnu.org \
--cc=unhammer@fsfe.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.