From: Ihor Radchenko <yantar92@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-ref-helm-insert-ref-link and latex src blocks
Date: Tue, 30 May 2023 11:52:34 +0000 [thread overview]
Message-ID: <87y1l6c9z1.fsf@localhost> (raw)
In-Reply-To: <87v8ga417g.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> #+begin_src latex :results latex replace :exports results :eval t
> \begin{equation}
> \label{eq:test:2}
>
> \end{equation}
> eqref:eq:test:2
> #+end_src
>
>
> There is some logic to it, however when I use org-edit-special
> to deal with the reference reftex-reference does do work, but gives the error
>
> ,----
> | Debugger entered--Lisp error: (error "RefTeX works only in buffers visiting a file")
> | signal(error ("RefTeX works only in buffers visiting a file"))
> | error("RefTeX works only in buffers visiting a file")
> | reftex-access-scan-info(nil)
> | reftex-reference()
> | funcall-interactively(reftex-reference)
> | call-interactively(reftex-reference nil nil)
> | command-execute(reftex-reference)
> |
> `----
This is expected because org-src buffers are not linked to any file.
They also do not provide any access to other latex src blocks in the file.
If you want to use RefTeX, you probably need to have pure LaTeX file. If
you want to use Org, org-ref will work better.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-30 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:29 org-ref-helm-insert-ref-link and latex src blocks Uwe Brauer
2023-05-30 11:52 ` Ihor Radchenko [this message]
2023-05-30 18:54 ` John Kitchin
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=87y1l6c9z1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).