From: Sven Bretfeld <email@example.com>
To: John Kitchin <firstname.lastname@example.org>
Cc: Emacs Orgmode <email@example.com>
Subject: Re: Links to external targets with (or despite) org-ref
Date: Wed, 22 Feb 2023 11:20:17 +0100 [thread overview]
Message-ID: <Y/XsYeCKC7LYpmUc@kamaloka> (raw)
That's working well. Thank you very much. And thousand thanks for
org-ref in general.
Am Mon, Feb 20, 2023 at 01:07:49PM -0500 schrieb John Kitchin:
> The quickest thing might be to remove the store properties on the ref links.
> This should do it.
> #+BEGIN_SRC emacs-lisp
> (cl-loop for reflink in '("ref" "pageref" "nameref" "eqref" "autoref" "cref"
> "Cref" "crefrange" "Crefrange")
> (setf (cdr (assoc reflink org-link-parameters))
> (org-plist-delete (cdr (assoc reflink org-link-parameters)) :store)))
> I guess I don't have that setup quite right in org-ref, it seems like it should
> not clobber other ways to store links.
> On Sun, Feb 19, 2023 at 10:39 AM Sven Bretfeld <firstname.lastname@example.org>
> Hi everybody
> I'm looking to create labels/links to specific text positions in org
> files (not line number, not header).
> I know that [[file:~/path_to_file::target]] can be used to jump to
> <<target>>. That would be fine and works for me -- IF I write the link
> However, org-ref which I use for citations seems to overwrite the
> default behaviour of org-store-link and org-insert-link. So when the
> point is on <<target>> and org-store-link is called (C-c l), I get a
> prompt "Store link with (default org-ref-store-ref)". No alternatives
> are offered when TAB is hit. Hiting RET saves the link as
> "Crefrange:target". A corresponding org-insert-link (C-c C-l) produces
> a link of the form [[Crefrange:target]] which, when in another file,
> of course leads nowhere ("search failed"). How to get the file name
> into these links without manually rewriting the link?
> I couldn't find anything on this issue in the org-ref manual or on the
> Thanks for help,
>  mailto:email@example.com
next prev parent reply other threads:[~2023-02-22 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 15:38 Links to external targets with (or despite) org-ref Sven Bretfeld
2023-02-20 18:07 ` John Kitchin
2023-02-22 10:20 ` Sven Bretfeld [this message]
2023-02-24 13:24 ` John Kitchin
2023-03-03 16:43 ` Ihor Radchenko
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 \
* 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).