From: Ihor Radchenko <yantar92@gmail.com>
To: William Denton <wtd@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Folded headlines with text showing where it shouldn't
Date: Tue, 12 Jul 2022 13:58:41 +0800 [thread overview]
Message-ID: <877d4i7tym.fsf@localhost> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2207120015490.34602@shell3.miskatonic.org>
William Denton <wtd@pobox.com> writes:
>> Usually, the problem you are seeing is when something is interfering
>> with 'invisible text property of links/other folded text.
>>
>> Can you post the value of org-link-parameters on your system?
>
> This is a new variable to me! I've never done anything with it, but it's got a
> lot in it.
>
> Value:
> (("attachment" :follow org-attach-follow :complete org-attach-complete-link)
> ("eww" :follow org-eww-open :store org-eww-store-link)
> ..
This is the default value.
>> You may also put the cursor onto unexpectedly visible link and check the
>> output of M-x describe-text-properties. Then, put the cursor right after
>> the link and run M-x describe-text-properties again. Then, share the
>> output.
>
> Here's a screenshot of the problem I get:
>
> https://www.miskatonic.org/tmp/org-problem.png
>
> And here's the output of describe-text-properties when the pointer is in the
> link that shouldn't be there:
>
> Text content at position 56157:
> ...
> There are 3 overlays here:
> From 56151 to 56168
> evaporate t
> invisible org-link-description
> isearch-open-invisible ignore
> isearch-open-invisible-temporary ignore
> org-invisible org-link-description
> priority 2
This is curious. Did the problem reveal itself after you used isearch
(C-s)? Do you happen to use some non-standard search package (like
evil)?
If you happen to see this issue again, what is the value of
org-fold-core--isearch-overlays inside that buffer?
Best,
Ihor
prev parent reply other threads:[~2022-07-12 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 1:52 Folded headlines with text showing where it shouldn't William Denton
2022-05-31 5:18 ` Ihor Radchenko
2022-06-02 21:32 ` William Denton
2022-06-03 6:30 ` Ihor Radchenko
2022-07-12 4:25 ` William Denton
2022-07-12 5:58 ` Ihor Radchenko [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d4i7tym.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.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/org-mode.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).