emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: File local circular links
Date: Fri, 4 Sep 2015 18:36:18 +0200	[thread overview]
Message-ID: <CALn3zogZCStBjQEGRGO=5jpEkRtmSAwi=BB33qqvdmSGPOoHdw@mail.gmail.com> (raw)
In-Reply-To: <87mvx3mwc4.fsf@nicolasgoaziou.fr>

Hi Nicolas

On Thu, Sep 3, 2015 at 4:06 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Can't you simply do
>
>   (org-link-search ":file local circular link:" (point))
>
> ?

In my previous example the

  (org-link-search "[[:file local circular link:]]" (point))

to get enough from the org-link-search argument AVOID-POS would work
to jump between the two links. But when the second link is in a
headline

-------------------------------------
[[:file local circular link:]]
some text
* [[:file local circular link:]]
-------------------------------------

the second link jumps only to itself with the new org-link-search. I
understand that this is desired behavior because the headline gets
priority over the target on line 1. Before your change the target on
line 1 was the match when following the link on line 3, which was a
bug that I wrongly relied on to jump backwards. My conclusion is that
org-link-search is the wrong function for my purpose and I will have
to implement something with re-search-forward on my own.

> You could also use target-links

My main requirement is that the link has to be also the target, not a
link and a target side by side. How could that be fulfilled with
target-links?

Michael

      reply	other threads:[~2015-09-04 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 13:42 File local circular links Michael Brand
2015-09-03 14:06 ` Nicolas Goaziou
2015-09-04 16:36   ` Michael Brand [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='CALn3zogZCStBjQEGRGO=5jpEkRtmSAwi=BB33qqvdmSGPOoHdw@mail.gmail.com' \
    --to=michael.ch.brand@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).