From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Julian Burgos <julian@hafro.is>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-ref & helm-bibtex notes
Date: Tue, 16 Jun 2015 21:25:09 -0400 [thread overview]
Message-ID: <m2lhfjf7nu.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <aeb2c5fa16040858a24122a7b87ba786.squirrel@webmail.hafro.is>
Julian Burgos writes:
> Dear list,
>
> I have been using org-ref for a while, using reftex to insert citations in
> my org documents. Now I am switching to helm-bibtex, which is pretty
> awesome. I have a couple of question about the note files. Org-ref uses
> a single file to keep notes (e.g. notes.org), but helm-bibtex assumes that
> notes are kept in separate files, one per article. My questions are:
>
> a) Do you have a preference in the single file vs multiple files question?
> Are advantages/disadvantages? I tend to prefer the single file option,
> it makes search easy and also I can add TODO items that later I can pull
> out in the agenda view.
I prefer the single file, for the reasons you describe.
> With multiple files this would not be as easy.
> Do you agree?
This is not totally true. You can add your directory of org notes to
your org-agenda-files, e.g.
(setq org-agenda-files '("~/path/to/org-notes"))
and it will add all org files in that directory to your agenda. If you
use helm, it is probably easy to search all of the files too.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-06-17 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 0:39 org-ref & helm-bibtex notes Julian Burgos
2015-06-17 1:21 ` Tory S. Anderson
2015-06-17 1:25 ` John Kitchin [this message]
2015-06-17 11:48 ` Julian Burgos
2015-06-17 1:28 ` Titus von der Malsburg
2015-06-17 12:25 ` Julian Burgos
2015-06-18 0:08 ` Titus von der Malsburg
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=m2lhfjf7nu.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=julian@hafro.is \
/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).