John Kitchin writes:
> If anyone knows how to use store functions that do not clobber the build in
> ones, I would be happy to update org-ref so you can use all the link store
> options.
This part of Org code has inconsistencies between the docstrings and the
implementation. https://orgmode.org/
You are welcome.
I also discovered just now that you can do C-u C-u C-c C-l to skip storing
functions that are not part of org-core.
If anyone knows how to use store functions that do not clobber the build in
ones, I would be happy to update org-ref so you can use all the link store
options.
On
Hi John
That's working well. Thank you very much. And thousand thanks for
org-ref in general.
Sven
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-
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")
do
(setf (cdr (assoc reflink org-link-parameters))
(org-plist-de
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
<>. That would be fine and works for me -- IF I write the link
manually.
However, org-ref which I use for cita
