emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 41584@debbugs.gnu.org, emacs-orgmode@gnu.org, dgutov@yandex.ru
Subject: Re: bug#41584: 26.3; org-indent-mode's line-prefix text property flickers near overlays
Date: Fri, 29 May 2020 10:12:27 +0300	[thread overview]
Message-ID: <83pnanqko4.fsf@gnu.org> (raw)
In-Reply-To: <87a71rhm3i.fsf@gmail.com> (message from =?iso-8859-1?Q?K=E9v?= =?iso-8859-1?Q?in?= Le Gouguec on Thu, 28 May 2020 21:54:09 +0200)

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Date: Thu, 28 May 2020 21:54:09 +0200
> Cc: emacs-orgmode@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
> - emacs -Q
> - C-x C-f repro.org
> - M-x org-indent-mode
> - M-: (insert "* heading\ntext")
> - M-:
> (let ((ov (make-overlay (point-at-bol) (point-at-bol)))
>       (val (propertize " " 'display '((left-fringe right-triangle)))))
>   (overlay-put ov 'before-string val))
> - RET
> - a
> When "a" is inserted, org-indent-mode's line-prefix disappears on the
> *previous* line ("text").  It remains gone as long as I type
> self-inserting characters, until
> - I type certain commands, e.g. RET or C-j, or
> - I insert a closing delimiter that makes
>   blink-paren-post-self-insert-function blink the corresponding opening
>   delimiter, e.g. ')' or ']'.
> Then the line-prefix shows up again.

In fact, it's enough to type "M-x".  Which is a clear sign that some
redisplay optimization kicks in where it shouldn't.  And indeed,
setting inhibit-try-window-id non-nil solves the problem.

I will look into this when I have time, thanks for an easy reproducer.

  reply	other threads:[~2020-05-29  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 19:54 26.3; org-indent-mode's line-prefix text property flickers near overlays Kévin Le Gouguec
2020-05-29  7:12 ` Eli Zaretskii [this message]
2020-05-29 14:03   ` bug#41584: " Eli Zaretskii
2020-05-29 18:11     ` Kévin Le Gouguec
2020-05-29 20:03       ` Eli Zaretskii
2020-05-29 20:32         ` Kévin Le Gouguec
2020-05-30  5:59           ` 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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pnanqko4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41584@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-orgmode@gnu.org \
    --cc=kevin.legouguec@gmail.com \


* 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


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).