emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: [DONE] Re: [BUG] The latest org-fold feature breaks link :activate-func property
Date: Fri, 29 Apr 2022 08:55:11 +0800	[thread overview]
Message-ID: <m2v8usbtc1.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <87bkwl90aw.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Ihor Radchenko <yantar92@gmail.com> writes:

> "Christopher M. Miles" <numbchild@gmail.com> writes:
>> I use extension [[https://repo.or.cz/org-link-beautify.git][org-link-beautify]] to display text-property beautify content on link. With
>> latest org-mode source code on commit "1ed9e4223", I got this error which displayed in the
>> attachment gif.
> I do not see any error there, except the fact that Org reveals the links
> contents.
> Looking at ol.el, it appears that org-next-link does not respect
> org-fold-show-context-detail (`link-search'). I fixed this problem on
> main.

Yes, that's the problem. I pulled that latest commit and confirmed the problem fixed. Thanks for
quick response!

> Let me know if you were referring to something else.
> Best,
> Ihor

[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2022-04-29  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <626a0713.1c69fb81.a3583.1a07SMTPIN_ADDED_BROKEN@mx.google.com>
2022-04-28  6:41 ` [BUG] The latest org-fold feature breaks link :activate-func property Ihor Radchenko
2022-04-28  8:17   ` Tim Cross
2022-04-29  0:55   ` Christopher M. Miles [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:

  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=m2v8usbtc1.fsf@numbchild@gmail.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).