From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG?: Link to inline-task not working
Date: Mon, 6 Dec 2021 14:14:09 +0100 [thread overview]
Message-ID: <CAP7OBx+Y=Bmz-deVvk3pFm53OQjO2Hs1UAbYyg_+rARQmA2e1A@mail.gmail.com> (raw)
In-Reply-To: <871r2tm4zk.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
>
> > Where are the links/href are built? There should be the error that
> excludes
> > inline-tasks.
>
> A quick search through the code yields: org-export-resolve-id-link
> It explicitly check headlines, but not inlinetasks.
>
Shouldn't be org-export-resolve-fuzzy-link the relevant function, at least
for my use case?
But there it looks like it is searching through all elements including
inlinetasks, which is in org-element-all-elements:
(append pseudo-types '(target) org-element-all-elements)
Am Sa., 4. Dez. 2021 um 04:18 Uhr schrieb Ihor Radchenko <yantar92@gmail.com
>:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > Where are the links/href are built? There should be the error that
> excludes
> > inline-tasks.
>
> A quick search through the code yields: org-export-resolve-id-link
> It explicitly check headlines, but not inlinetasks.
> The fix should not be too hard. Feel free to send a patch ;)
>
> Best,
> Ihor
>
[-- Attachment #2: Type: text/html, Size: 1593 bytes --]
next prev parent reply other threads:[~2021-12-06 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 8:30 BUG?: Link to inline-task not working Michael Dauer
2021-12-03 10:51 ` Ihor Radchenko
2021-12-03 14:20 ` Michael Dauer
2021-12-04 3:19 ` Ihor Radchenko
2021-12-06 13:14 ` Michael Dauer [this message]
2021-12-06 13:47 ` Ihor Radchenko
2022-10-05 3:23 ` [org-export] Linking inlinetasks (was: BUG?: Link to inline-task not working) Ihor Radchenko
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='CAP7OBx+Y=Bmz-deVvk3pFm53OQjO2Hs1UAbYyg_+rARQmA2e1A@mail.gmail.com' \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.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).