From: Eli Zaretskii <eliz@gnu.org>
To: Paul Rankin <hello@paulwrankin.com>
Cc: 30432@debbugs.gnu.org
Subject: bug#30432: 26.0.91; freeze when text wrap-prefix exceeds window text width
Date: Tue, 13 Feb 2018 07:15:13 +0200 [thread overview]
Message-ID: <833725zd0e.fsf@gnu.org> (raw)
In-Reply-To: <9C3F79F1-DCBD-42C9-B105-FA03A8911270@paulwrankin.com> (message from Paul Rankin on Tue, 13 Feb 2018 12:15:17 +1000)
> From: Paul Rankin <hello@paulwrankin.com>
> Date: Tue, 13 Feb 2018 12:15:17 +1000
> Cc: 30432@debbugs.gnu.org
>
> Sorry I didn't include my system before:
>
> macOS High Sierra 10.13.3 (17D47)
> MacBook Pro (Retina, 15-inch, Mid 2015)
> Emacs.app built from emacs-26 branch
Yes, I tried the emacs-26 branch as well. What I reported was from
that branch's build.
> It's definitely a freeze. Emacs becomes unresponsive and needs to be force quit.
Did you try C-g 2 or 3 times? If so, did it help?
> I can understand that the real-world use case might not make sense to your own use of Emacs, but in the use I described, it means Emacs freezes by just changing the font size... not good.
I agree the result is not good even if Emacs behaves like it does on
my system, which is not a total freeze. I'll try to see if I can find
some reasonable way out of this situation.
next prev parent reply other threads:[~2018-02-13 5:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 6:49 bug#30432: 26.0.91; freeze when text wrap-prefix exceeds window text width Paul Rankin
2018-02-12 19:51 ` Eli Zaretskii
2018-02-13 2:15 ` Paul Rankin
2018-02-13 2:18 ` Paul Rankin
2018-02-13 2:30 ` Paul Rankin
2018-02-13 5:15 ` Eli Zaretskii [this message]
2018-02-13 5:57 ` Paul Rankin
2018-03-20 17:10 ` Eli Zaretskii
2018-03-29 5:00 ` Paul W. Rankin
2018-03-30 12:59 ` Eli Zaretskii
2018-05-07 18:38 ` Eli Zaretskii
[not found] ` <0C03687D-D0D4-46CE-B409-6A2E55C8A5FA@paulwrankin.com>
[not found] ` <2F164141-0F75-45C9-8211-ADAF2B005C16@paulwrankin.com>
2018-05-08 17:16 ` 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=833725zd0e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30432@debbugs.gnu.org \
--cc=hello@paulwrankin.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).