From: Paul Rankin <hello@paulwrankin.com>
To: Eli Zaretskii <eliz@gnu.org>
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 12:30:27 +1000 [thread overview]
Message-ID: <7E549FDE-603E-4CE9-BBDF-62D9C3055007@paulwrankin.com> (raw)
In-Reply-To: <284C16BC-D7E0-47EA-8A7B-F6AEFAAD0147@paulwrankin.com>
This video has the whole show. I select a paragraph of lorem ipsum, put the wrap-prefix of 90 and then zap, Emacs becomes a zombie.
https://gfycat.com/WarpedImpureFlickertailsquirrel
In the vid I'm both clicking and hitting C-b, M-<, etc. but nothing.
--
https://www.paulwrankin.com
> On 13 Feb 2018, at 12:18 pm, Paul Rankin <hello@paulwrankin.com> wrote:
>
> On 13 Feb 2018, at 12:15 pm, Paul Rankin <hello@paulwrankin.com> wrote:
>>
>> It's definitely a freeze. Emacs becomes unresponsive and needs to be force quit. I've recorded a video showing how it all goes down:
>>
>> https://gfycat.com/gifs/detail/ImmaculateLazyAfricanjacana
>
> Sorry, I didn't realise this video site is truncated to 60 seconds, which doesn't adequately illustrate the issue. I'm uploading a new one now.
next prev parent reply other threads:[~2018-02-13 2:30 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 [this message]
2018-02-13 5:15 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E549FDE-603E-4CE9-BBDF-62D9C3055007@paulwrankin.com \
--to=hello@paulwrankin.com \
--cc=30432@debbugs.gnu.org \
--cc=eliz@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.