From: Robert Irelan <rirelan@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Feature request: Allow clocktable :link to use IDs rather than fuzzy search in links
Date: Thu, 19 Dec 2019 18:46:08 -0800 [thread overview]
Message-ID: <CAJUyYjrQ5Qn35HK14OPLKC6CV4ZNoUvXBrxqtsyVFXdJgEPrfg@mail.gmail.com> (raw)
In-Reply-To: <CAJUyYjrUepDtN0Uu_gy1VHMvYZCnE44Hmk7i1TBN-vpeOGsUWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Now that Org 9.3 has been released, I'd like to bring this issue up again.
On Wed, Sep 25, 2019 at 1:13 PM Robert Irelan <rirelan@gmail.com> wrote:
> The :link header argument on clock tables (see
> https://orgmode.org/manual/The-clock-table.html) currently generates
> links that use fuzzy search when `:link t` is set. I'd like to propose
> that this setting respect `org-id-link-to-org-use-id`. For example, if
> I have `org-id-link-to-org-use-id` set to `t`, I'd like to have an ID
> created for the entry in the clock table, if necessary, and then
> create the link in the table using the ID instead of a search.
>
> Context: I'm currently trying to publish an Org file that contains my
> daily journal entries. In every entry, I generate clock tables
> containing the tasks I've clocked time on that day. However, some of
> the entries link to headlines that no longer exist. For whatever
> reason, setting `org-export-with-broken-links` doesn't work to avoid
> aborting the export whenever it encounters a fuzzy search link that
> can't be resolved.
>
> --
> Robert Irelan
> rirelan@gmail.com
>
--
Robert Irelan
rirelan@gmail.com
[-- Attachment #2: Type: text/html, Size: 1789 bytes --]
prev parent reply other threads:[~2019-12-20 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 20:13 Feature request: Allow clocktable :link to use IDs rather than fuzzy search in links Robert Irelan
2019-12-20 2:46 ` Robert Irelan [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=CAJUyYjrQ5Qn35HK14OPLKC6CV4ZNoUvXBrxqtsyVFXdJgEPrfg@mail.gmail.com \
--to=rirelan@gmail.com \
--cc=emacs-orgmode@gnu.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/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).