From: Christoph Groth <christoph@grothesque.org>
To: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Wed, 10 Sep 2014 12:31:33 +0200 [thread overview]
Message-ID: <87ha0fzrzu.fsf@grothesque.org> (raw)
In-Reply-To: 87zje8u404.fsf@yale.edu
Jorge A. Alfaro-Murillo wrote:
> Thomas S. Dye writes:
>
>> I don't manage my bibliography references in Org mode. I am used to
>> managing a bibtex database and have never found the need to move
>> everything to Org.
>
> Same here.
My motivation for keeping bibliography in org was to keep all local
information about a paper (including notes and comments) in one place.
This should make it easier to find it.
Meanwhile I found org-bibtex. It seems to implement just what I had in
mind and is even included in orgmode by default. The following function
can be used to save a org-bibtex headline into the kill-ring in bib
format, so that it can be yanked into a project-specific .bib-file:
(defun my-org-bibtex-kill-ring-save-headline ()
(interactive)
(kill-new (org-bibtex-headline)))
>> Either a separate bibtex file for each article, or separate bibtex
>> files for each co-author.
>
> Or better do both...
>
> #+BEGIN_SRC latex
> \bibliography{/home/you/references/articles.bib}
> % \bibliography{/home/collaborator_1/references/articles.bib}
> % \bibliography{/home/collaborator_2/references/articles.bib}
> ...
> \bibliography{references}
>
> #+END_SRC
>
> When a collaborator_i is working on the file she/he comments the first
> line and uncomments the i-th line AND everybody runs
> reftex-create-bibtex-file (or copy paste the new references for the
> unfortunate non-emacs user) after adding new references and finishing
> editing. Everybody shares a current version of the .tex file and the
> references.bib file.
I like to keep papers under version control, and the commenting that you
suggest does not seem to fit this way of working very well.
next prev parent reply other threads:[~2014-09-10 10:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 20:50 Managing articles in orgmode and collaboration Christoph Groth
2014-09-09 9:13 ` Christoph Groth
2014-09-09 10:48 ` Thorsten Jolitz
2014-09-09 11:40 ` Christoph Groth
2014-09-09 12:18 ` Vikas Rawal
2014-09-09 12:24 ` Fabrice Popineau
2014-09-09 12:48 ` Thorsten Jolitz
2014-09-09 14:22 ` Samuel Loury
2014-09-09 20:25 ` John Kitchin
2014-09-09 16:34 ` Thomas S. Dye
2014-09-09 16:56 ` Jorge A. Alfaro-Murillo
2014-09-09 17:30 ` Rasmus
2014-09-10 10:31 ` Christoph Groth [this message]
2014-09-10 14:33 ` Jorge A. Alfaro-Murillo
2014-09-23 13:14 ` Christoph Groth
2014-09-23 13:52 ` Jorge A. Alfaro-Murillo
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=87ha0fzrzu.fsf@grothesque.org \
--to=christoph@grothesque.org \
--cc=emacs-orgmode@gnu.org \
/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).