* Should org-get-outline-path strip dedicated targets?
@ 2016-06-03 12:24 timor
2016-06-11 8:19 ` Nicolas Goaziou
0 siblings, 1 reply; 3+ messages in thread
From: timor @ 2016-06-03 12:24 UTC (permalink / raw)
To: emacs-orgmode
If I have a document like this:
* some header <<some_target>>
** some subtree
*** some entry
Then calling org-get-outline-path on the deepest headline returns
("some header <<some_target>>" "some subtree")
I don't know what exactly org-get-outline-path is used for in org
mode, but for what I want to use it, I will remove the
"<<some_target>>" part manually.
I was just wondering if maybe this should already be done in
org-get-outline-path itself, since links are also replaced by their
description according to the documentation.
regards,
timor
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Should org-get-outline-path strip dedicated targets?
2016-06-03 12:24 Should org-get-outline-path strip dedicated targets? timor
@ 2016-06-11 8:19 ` Nicolas Goaziou
2016-06-16 10:11 ` timor
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2016-06-11 8:19 UTC (permalink / raw)
To: timor; +Cc: emacs-orgmode
Hello,
timor <timor.dd@gmail.com> writes:
> If I have a document like this:
>
> * some header <<some_target>>
> ** some subtree
> *** some entry
>
> Then calling org-get-outline-path on the deepest headline returns
> ("some header <<some_target>>" "some subtree")
>
> I don't know what exactly org-get-outline-path is used for in org
> mode, but for what I want to use it, I will remove the
> "<<some_target>>" part manually.
>
> I was just wondering if maybe this should already be done in
> org-get-outline-path itself, since links are also replaced by their
> description according to the documentation.
Links and targets are different in the sense that the former has an
invisible part, unlike to the latter. `org-get-outline-path' simply
removes that part since users probably do not distinguish their headings
using hidden characters.
OTOH, it could make sense to preserve targets, e.g., in the following:
* Doc 1
** Introduction <<intro1>>
...
* Doc 2
** Introduction <<intro2>>
...
Eventually, albeit tangential to the problem, I think using a CUSTOM_ID
is probably better than inserting a target in a headline.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Should org-get-outline-path strip dedicated targets?
2016-06-11 8:19 ` Nicolas Goaziou
@ 2016-06-16 10:11 ` timor
0 siblings, 0 replies; 3+ messages in thread
From: timor @ 2016-06-16 10:11 UTC (permalink / raw)
To: emacs-orgmode, mail
Hello Nicolas,
Custom IDs seem to be a good alternative here, although I would think
about the <<target>> part as an invisible part, since I don't expect
it to be visible for e.g. export.
Thanks.
Regards,
timor
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-06-16 10:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-03 12:24 Should org-get-outline-path strip dedicated targets? timor
2016-06-11 8:19 ` Nicolas Goaziou
2016-06-16 10:11 ` timor
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).