From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Xebar Saram <zeltakc@gmail.com>
Cc: Julian Burgos <julian@hafro.is>,
emacs-orgmode <emacs-orgmode@gnu.org>, windy <chxp_moon@163.com>,
Ken Mankoff <mankoff@gmail.com>,
Holger Wenzel <drholgerwenzel@gmail.com>
Subject: Re: Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :)
Date: Sat, 13 Jun 2015 15:52:54 -0400 [thread overview]
Message-ID: <CAJ51ETrVpbNmxifymOCtc59ddMyZEod2TF22kQYR=R8JtLdQvw@mail.gmail.com> (raw)
In-Reply-To: <CAOQHXPoy+UXMZD0653kzkJ-g5t_iP5_+FciDfk2SzWLS-WkjDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4014 bytes --]
I guess you could say I use it to manage my references. E.g. I add
references using the functions in doi-utils.el. I can search them using
helm-bibtex (which is not part of org-ref, we just use it because it is
awesome), and from that I can see groups of references with keywords,
etc... helm-bibtex provides the "table"view I think you are referring to as
a helm selection buffer. Alternatively in org-ref you could use the older
reftex interface.
When I click on a cite link, there actions available to do things like
open the entry, find related articles, etc...
(org-ref-build-full-bibliography) allows you to build a pdf version of a
bibtex file pretty conveniently.
the jmax-bibtex.el file in org-ref provides additional functionality to
clean up bibtex entries, etc...
so, it is fair to say emacs+org-ref+helm-bibtex is how I manage my
references, and use them in writing.
John
-----------------------------------
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
On Sat, Jun 13, 2015 at 3:06 PM, Xebar Saram <zeltakc@gmail.com> wrote:
> Hi list and John
>
> Thank you all for all the great advice i will start incorporating them
> into my daily workflow
>
> John: org-ref looks great but is it also used for "managing" you
> references? that is searching for entries, grouping by keys, exporting them
> to html, adding etc. does it have a "table" view or other? if not what do
> you use for managing your references?
>
> best
>
> Z
>
> On Fri, Jun 12, 2015 at 5:02 PM, Ken Mankoff <mankoff@gmail.com> wrote:
>
>> Hi Julian,
>>
>> On 2015-06-10 at 10:16, Julian Burgos <julian@hafro.is> wrote:
>> > a) I first write in org-mode. Export to Word, either exporting first
>> > to ODT and then to Word, or to LaTex and then use pandoc to convert
>> > LaTex to Word. My coauthor can edit the document as he wishes, using
>> > the "Track changes" option. Then, I transcribe their edits back into
>> > the org-mode document. Advantage of this approach: your coauthor
>> > receives a clean word file, that could include figures, references,
>> > etc., and he/she uses the tools she likes to edit the file.
>> > Disadvantage: you have to manually incorporate the changes to the
>> > org-mode file each time there are edits.
>> >
>> > b) I write the manuscript in org-mode. Then I send the org-mode file
>> > to my coauthor. Because the org-mode file is just a text file, my
>> > coauthor can use Word to edit it. I ask him/her *not* to use "track
>> > changes" and to save the edited version also as a text file. Then,
>> > when I receive it I use ediff in emacs to compare both documents and
>> > incorporate the edits I want. Advantage of this approach: the merging
>> > of the documents is easy using ediff. Disadvantage: your coauthor has
>> > to edit a weird-looking document, with markup, code blocks, etc.
>>
>> It seems like with a bit of extra (scriptable?) work you could remove
>> both disadvantages.
>>
>> Why can't you use method (a) above, and then DOCX -> Org via pandoc (with
>> --accept-all option)?
>>
>> I know pandoc introduce some of its own changes to the Org syntax but not
>> the document itself. You can get around this. You can remove the
>> pandoc-generated changes automagically so that only co-author changes
>> appear in Org format, which you can then use with your (b) above and emacs
>> ediff.
>>
>> Original: Your Org source
>> A: Org -> DOCX for co-authors (using pandoc)
>> B: Org -> DOCX -> Org (using pandoc).
>> C: A -> Org (using pandoc and --accept-all-changes)
>> D: B-Original
>>
>> The difference between B and Original are pandoc-introduced changes that
>> you do not want. Ignore/remove these changes from C, call it D and then the
>> difference between D and the Original are your co-author comments. Now your
>> authors can edit DOCX with Track Changes and you can work on those edits
>> with Emacs ediff.
>>
>> -k.
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 5336 bytes --]
next prev parent reply other threads:[~2015-06-13 19:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 16:39 Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :) Xebar Saram
2015-06-08 21:16 ` M
2015-06-09 5:13 ` Xebar Saram
2015-06-09 7:00 ` Holger Wenzel
2015-06-09 13:21 ` John Kitchin
2015-06-10 1:57 ` windy
2015-06-10 13:49 ` John Kitchin
2015-06-10 14:14 ` Ken Mankoff
2015-06-10 20:58 ` Titus von der Malsburg
2015-06-11 5:30 ` Rasmus
2015-06-11 14:56 ` Phillip Lord
2015-06-11 17:02 ` John Kitchin
2015-06-12 13:24 ` Phillip Lord
2015-06-10 14:16 ` Julian Burgos
2015-06-11 2:07 ` windy
2015-06-11 5:38 ` Rasmus
2015-06-11 12:19 ` windy
2015-06-11 12:18 ` Ken Mankoff
2015-06-11 12:54 ` windy
2015-06-12 14:02 ` Ken Mankoff
2015-06-13 19:06 ` Xebar Saram
2015-06-13 19:52 ` John Kitchin [this message]
2015-06-15 17:33 ` Julian Burgos
2015-06-16 1:49 ` Bob Newell
2015-06-16 23:15 ` Alan L Tyree
2015-06-10 18:51 ` Eric S Fraga
2015-06-09 9:49 ` Alan Schmitt
2015-08-26 14:17 ` Anders Johansson
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='CAJ51ETrVpbNmxifymOCtc59ddMyZEod2TF22kQYR=R8JtLdQvw@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=chxp_moon@163.com \
--cc=drholgerwenzel@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=julian@hafro.is \
--cc=mankoff@gmail.com \
--cc=zeltakc@gmail.com \
/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).