From: Ramon Diaz-Uriarte <rdiaz02@gmail.com>
To: org mode <emacs-orgmode@gnu.org>
Cc: ramon.diaz@iib.uam.es
Subject: more helm-bibtex/org-ref questions
Date: Fri, 26 Jun 2015 22:33:28 +0200 [thread overview]
Message-ID: <87mvzmp5uv.fsf@gmail.com> (raw)
Dear All,
(I am not sure this is the appropriate place, but this is neither a bug
report nor an feature request about helm-bibtex or org-ref, but a question
from ignorance and I am learning quite a bit from the other helm-bibtex
questions).
How do people deal with multiple files that are logically associated to an
entry?
I've been used to keeping the main file, supplementary materials,
associated code, etc, in a directory per entry. This kind of modus operandi
is something I adopted (fell into?) easily with Zotero and Mendeley. But I
am not sure that this is the best way to proceed.
If I end up with multiple files per directory, helm-bibtex-find-pdf[1]
cannot know which one I want to open. I could keep the main file in the
general directory, so it is found directly by helm-bibtex-find-pdf and
specify other files (of secondary usage) in the "file" field (and maybe
open them via ebib when/if needed)? But this does not seem
elegant. Another is to have an entry per file, with unique key, but this
does not seem right.
Thanks,
R.
[1] Thanks to Titus' help
(https://github.com/tmalsburg/helm-bibtex/issues/53), opening a PDF that is
given in the "file" field with the directory name is now within my reach.
--
Ramon Diaz-Uriarte
Department of Biochemistry, Lab B-25
Facultad de Medicina
Universidad Autónoma de Madrid
Arzobispo Morcillo, 4
28029 Madrid
Spain
Phone: +34-91-497-2412
Email: rdiaz02@gmail.com
ramon.diaz@iib.uam.es
http://ligarto.org/rdiaz
next reply other threads:[~2015-06-26 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 20:33 Ramon Diaz-Uriarte [this message]
2015-06-26 20:58 ` more helm-bibtex/org-ref questions John Kitchin
2015-06-27 10:15 ` Ramon Diaz-Uriarte
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=87mvzmp5uv.fsf@gmail.com \
--to=rdiaz02@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ramon.diaz@iib.uam.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).