From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: E Sabof <esabof@gmail.com>, 14582@debbugs.gnu.org
Subject: bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay.
Date: Mon, 31 Jan 2022 01:36:41 +0100 [thread overview]
Message-ID: <87k0egwxk6.fsf@web.de> (raw)
In-Reply-To: <87czk87vmo.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 30 Jan 2022 22:37:35 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Are you still seeing this issue in recent Emacs versions? If so, do
> you have a more complete recipe to reproduce the problem?
AFAIU, I still see this.
The effect is that the first visual line in the folded buffer looks like
...
i.e. consists of just three eliding dots, but when I scroll up, I see
that the dots belong to e.g.
(progn...)
I see that all the time when working with hideshow, and it's quite
annoying.
Lars, you just need to follow the recipe of the OP in an Elisp buffer
containing some code to reproduce the issue. You maybe need to repeat a
second time (unfold + refold again).
If still not lucky, I'll try to create a step-by-step recipe, but maybe
it's clear enough. And I hope I did not misinterpret the original
report.
Michael.
next prev parent reply other threads:[~2022-01-31 0:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 9:13 bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay E Sabof
2013-06-09 17:06 ` Eli Zaretskii
2013-06-09 17:37 ` E Sabof
2013-06-09 17:52 ` Eli Zaretskii
2013-06-09 18:16 ` E Sabof
2013-06-09 18:25 ` Eli Zaretskii
2013-06-09 18:40 ` E Sabof
2013-06-09 18:49 ` E Sabof
2022-01-30 21:37 ` Lars Ingebrigtsen
2022-01-31 0:36 ` Michael Heerdegen [this message]
2022-01-31 14:57 ` Eli Zaretskii
2022-01-31 18:42 ` Michael Heerdegen
2022-01-31 19:08 ` Eli Zaretskii
2022-02-01 3:03 ` Michael Heerdegen
2022-02-01 18:18 ` Eli Zaretskii
2022-02-02 1:12 ` Michael Heerdegen
2022-02-02 3:34 ` Eli Zaretskii
2022-02-02 4:02 ` Michael Heerdegen
2022-02-02 12:31 ` Eli Zaretskii
2022-02-03 17:40 ` Eli Zaretskii
2022-02-04 1:37 ` Michael Heerdegen
2022-02-04 13:56 ` Eli Zaretskii
2022-02-06 2:54 ` Michael Heerdegen
2022-02-06 10:28 ` Eli Zaretskii
2022-02-08 0:29 ` Michael Heerdegen
2022-02-08 3:34 ` Eli Zaretskii
2022-02-08 4:05 ` Michael Heerdegen
2022-02-08 12:23 ` Eli Zaretskii
2022-02-09 0:20 ` Michael Heerdegen
2022-02-09 3:53 ` Michael Heerdegen
2022-02-09 13:47 ` Eli Zaretskii
2022-02-10 1:07 ` Michael Heerdegen
2022-02-10 6:15 ` Eli Zaretskii
2022-02-11 4:42 ` Michael Heerdegen
2022-02-11 8:46 ` Eli Zaretskii
2022-02-12 0:25 ` Michael Heerdegen
2022-02-12 7:28 ` Eli Zaretskii
2022-02-12 22:53 ` Michael Heerdegen
2022-02-13 11:43 ` Eli Zaretskii
2022-02-27 3:54 ` Michael Heerdegen
2022-02-27 8:08 ` Eli Zaretskii
2022-02-27 23:19 ` Michael Heerdegen
2022-02-28 13:10 ` Eli Zaretskii
2022-01-31 15:30 ` Lars Ingebrigtsen
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=87k0egwxk6.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=14582@debbugs.gnu.org \
--cc=esabof@gmail.com \
--cc=larsi@gnus.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 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).