From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: npostavs@users.sourceforge.net
Cc: 25246@debbugs.gnu.org
Subject: bug#25246: 25.1.90; Buffer not responsible with overlay at buffer end.
Date: Fri, 23 Dec 2016 08:33:15 +0100 [thread overview]
Message-ID: <20161223073315.GD5148@seven> (raw)
In-Reply-To: <87wpera4y3.fsf@users.sourceforge.net>
Mail von npostavs@users.sourceforge.net, Thu, 22 Dec 2016 at 19:01:56 -0500:
Hello,
> > It should be enough to provide some text to serve as buffer contents,
> > and a Lisp function to put the overlay on that text, such that Emacs
> > stops responding.
>
> I think the OP already provided those. Here's some elisp code to
> reproduce the problem based on the description (some adjustment may be
> needed depending on display width):
thanks for the programatically recipe. I will do it better next time.
And yes this shows the bad behaviour.
Also I can confirm that with version from master branch, namely
@ origin/master origin/HEAD a978d300a3faf58ee6e94ba57f764ca99a9ec308
Author: Mark Oteiza <mvoteiza@udel.edu>
AuthorDate: Thu Dec 22 19:09:01 2016 -0500
the problem has gone on both systems, Linux and Windows.
(Little odd ting is the blinking of the overlay, but it's ok.)
With kind regards,
Stefan
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
next prev parent reply other threads:[~2016-12-23 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 9:13 bug#25246: 25.1.90; Buffer not responsible with overlay at buffer end Stefan-W. Hahn
2016-12-22 13:55 ` npostavs
2016-12-22 17:04 ` Eli Zaretskii
2016-12-23 0:01 ` npostavs
2016-12-23 7:33 ` Stefan-W. Hahn [this message]
2016-12-23 9:21 ` Eli Zaretskii
2016-12-23 11:08 ` Eli Zaretskii
2016-12-23 13:36 ` Stefan-W. Hahn
2016-12-23 13:53 ` npostavs
2016-12-23 14:16 ` Stefan-W. Hahn
2016-12-23 13:57 ` Eli Zaretskii
2016-12-23 14:14 ` npostavs
2016-12-23 14:19 ` 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=20161223073315.GD5148@seven \
--to=stefan.hahn@s-hahn.de \
--cc=25246@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.