emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: File local circular links
Date: Thu, 03 Sep 2015 16:06:03 +0200	[thread overview]
Message-ID: <87mvx3mwc4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALn3zojAzOvtaowPR2imSiA=5i4PhpEWU6_AfPtbByS4eLiOyw@mail.gmail.com> (Michael Brand's message of "Thu, 3 Sep 2015 15:42:38 +0200")

Hello,

Michael Brand <michael.ch.brand@gmail.com> writes:

> I use a hack to work around a missing feature that I would like to
> call "file local circular links". It works until
> release_8.2.10-2341-g8094d01 but stops with
> release_8.2.10-2342-gcfe5bc9
>
>     commit cfe5bc97f8b18ccbf49d0764746c7563ce8d29da
>     Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
>     Date:   Mon Aug 3 01:06:32 2015 +0200
>
>         Fix link search
>
> and I would like to ask for some help to get it work again.
>
> File local circular links does this: C-c C-o on line 1 of the file
>
> -------------------------------------
> [[:file local circular link:]]
> some text
> [[:file local circular link:]]
> -------------------------------------
>
> moves to line 3 and C-c C-o again moves back to line 1. (It does not
> follow all links when there are more than two but this limitation is a
> different story.)
>
> The hack that I used so far is
>
> #+BEGIN_SRC emacs-lisp
>   (defun f-org-link-exec (str)
>     (let* ((context (org-element-context))
>            (link (let ((up (org-element-property :parent context)))
>                    (if (eq (org-element-type up) 'link) up context)))
>            (avoid-pos (org-element-property :begin link)))
>       (cond
>        ;; [[<<xy>>]]: Remove the angular brackets to let `org-link-search'
>        ;; match `str' as an angular bracket link.
>        ((string-match "^<<\\(.*\\)>>$" str)
>         (let ((org-execute-file-search-functions nil))
>           (org-link-search (match-string 1 str) 'dedicated avoid-pos)))
>        ;; [[_:xy:]] (abbreviated with "#+LINK: _ file:bla.org:::") or
>        ;; [[:xy:]]: Bind `org-link-search-must-match-exact-headline' to nil
>        ;; temporarily.
>        ((string-match-p "^:.*:$" str)
>         (let ((org-execute-file-search-functions nil)
>               (org-link-search-must-match-exact-headline nil))
>           ;; The leading part may be "[[link_abbreviation" or just "[[".
>           (org-link-search (concat "\\[\\[[^:]*" (regexp-quote str) "\\]\\]")
>                            'fuzzy avoid-pos))))))
>   (add-hook 'org-execute-file-search-functions 'f-org-link-exec)
> #+END_SRC
>
> The problematic part is the use of org-link-search which changed. In
> the above example it is called as
>
> #+BEGIN_SRC emacs-lisp
>   (let ((org-execute-file-search-functions nil)
>         (org-link-search-must-match-exact-headline nil))
>     (org-link-search "\\[\\[[^:]*:file local circular link:\\]\\]"))
> #+END_SRC
>
> and after the commit org-link-search errors with "cond: No match for
> fuzzy expression: \[\[[^:]*:file local circular link:\]\]". To me it
> looks like if support for regular expressions for fuzzy links has been
> dropped. I can not use the regexp search here because it invokes the
> org-occur sparse tree.

I don't know anything like regular expression support for fuzzy links.

> How can I deal with this?

Can't you simply do

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

?

You could also use target-links, or define a new type of link that would
trigger a search in the buffer, see `org-add-link-type'.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-09-03 14:04 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 [this message]
2015-09-04 16:36   ` Michael Brand

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=87mvx3mwc4.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@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).