emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Julian L <julianlpc15@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Behavior of links
Date: Wed, 25 Nov 2020 01:08:12 -0500	[thread overview]
Message-ID: <87ft4y7yur.fsf@kyleam.com> (raw)
In-Reply-To: <CAJ4nLVA_YKR7ehwvqL44Zri4N05r2ZsADYrBWz8UtaKG6NWofw@mail.gmail.com>

Julian L writes:

> Hi!
> Following this github issue in org-roam
> <https://github.com/org-roam/org-roam/issues/1317>, I would like to ask
> about the behavior of links in org mode. More specifically, let's say I
> have this headline:
> * my heading
> :GOAL: I want to be able to say [[file:something.org]]
> :END:
> [[file:language.org]]
> :END:
> According to the issue, links in the properties drawer aren't considered
> links by org mode (even though I can click on them and they work fine), but
> on the other hand links on a separate drawer like RELATED are considered
> links.

Right, according to Org syntax, file:something.org is not a link.  With
point on it, org-element-context returns

    (:key "GOAL" :value "I want to be able to say [[file:something.org]]" ...))

Compare that to file:language.org:

  (link (:type "file" :path "language.org"  ...))

Here are some links that might be helpful:


> How stable is this behavior? Is it expected to change in the future?

As far as I know, it's been around since org-element.el was introduced
in core (2012), and I'm aware of no plans to change it.

      reply	other threads:[~2020-11-25  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 10:04 Behavior of links Julian L
2020-11-25  6:08 ` Kyle Meyer [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=87ft4y7yur.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julianlpc15@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).