emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Julian Burgos" <julian@hafro.is>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Julian Burgos <julian@hafro.is>, emacs-orgmode@gnu.org
Subject: Re: org-ref & helm-bibtex notes
Date: Wed, 17 Jun 2015 11:48:52 -0000	[thread overview]
Message-ID: <54b67ff307814d7d13e310ca993b835c.squirrel@webmail.hafro.is> (raw)
In-Reply-To: <m2lhfjf7nu.fsf@andrew.cmu.edu>

Thanks John.  You are right, although I think having to read too many org
files would make the agenda run slower.  And creates a lot of buffers (one
per file) which makes navigation more complicated.  I always wished that
the agenda would close those buffers.  Anyway, I think that having a
single file is the best option.

>
> 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
>

  reply	other threads:[~2015-06-17 11:49 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
2015-06-17 11:48   ` Julian Burgos [this message]
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=54b67ff307814d7d13e310ca993b835c.squirrel@webmail.hafro.is \
    --to=julian@hafro.is \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).