From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: A book produced using Org Date: Sun, 20 Sep 2015 19:27:36 -0400 Message-ID: References: <6F8ECF8A-D17C-4A27-878B-D0C98E064C77@agrarianresearch.org> <8B0CE483-900A-4128-9292-0C5FECB2F8AC@agrarianresearch.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46409) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zdo1F-0007CL-Jq for emacs-orgmode@gnu.org; Sun, 20 Sep 2015 19:27:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zdo1C-00032s-EH for emacs-orgmode@gnu.org; Sun, 20 Sep 2015 19:27:41 -0400 Received: from mail-qg0-x22d.google.com ([2607:f8b0:400d:c04::22d]:33120) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zdo1C-00032h-9h for emacs-orgmode@gnu.org; Sun, 20 Sep 2015 19:27:38 -0400 Received: by qgev79 with SMTP id v79so77454399qge.0 for ; Sun, 20 Sep 2015 16:27:38 -0700 (PDT) In-reply-to: <8B0CE483-900A-4128-9292-0C5FECB2F8AC@agrarianresearch.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Vikas Rawal Cc: org-mode mailing list , Manuel Koell I also pretty routinely use two org files that are about 15000 lines long, in exactly the same way you describe below. One is a book on using Python in Science and engineering, and one is using Python to do molecular simulations with density functional theory. Both have at least 100 code block examples in them. It works great! Vikas Rawal writes: >> >> Beautiful! I would love to see the org file! How did emacs perform which such huge file? >> > > Emacs had no trouble whatsoever. The main file is 9313 lines. > > I turned off evaluation of code blocks at export time. Many of the code blocks download data from FAO and other websites before using them. Evaluating all of them at export time would have meant too much lag in producing the pdf. So all code blocks had to be manually evaluated (C-c C-c), if I changed anything. > > I did not manage to learn and use export filters. There were a couple of things that I needed to fix at the time of export. Since I could not handle those in org, I wrote a bash script that would use sed to clear up those things, and then create a pdf. But that was it. > > Although I do not know git very well, I can manage basic operations. I had a git repo to deal with versions. In the end, there were two versions: one that laid out the page on a larger stock paper with trim marks for the printer, and another that generated the online version for the FAO document repository. > > Let me put the files in a github repo and share the link. > > Vikas -- 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