From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Best practices for literate programming [was: Latex export of tables] Date: Thu, 18 Apr 2013 18:53:50 +0200 Message-ID: <877gjzsrtt.fsf@pank.eu> References: <20130412080600.GA18235@panahar> <20130414232953.GC11696@kuru.dyndns-at-home.com> <20130416115619.GA12405@panahar> <20130416173948.GC7402@kuru.dyndns-at-home.com> <20130416221022.GA7809@panahar> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34612) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USs5x-0006U4-42 for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 12:54:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1USs5v-0001Ng-Se for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 12:54:01 -0400 Received: from plane.gmane.org ([80.91.229.3]:60583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USs5v-0001Na-Lp for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 12:53:59 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1USs5u-0004C0-G3 for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 18:53:58 +0200 Received: from dynamic-adsl-94-34-137-181.clienti.tiscali.it ([94.34.137.181]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Apr 2013 18:53:58 +0200 Received: from rasmus by dynamic-adsl-94-34-137-181.clienti.tiscali.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Apr 2013 18:53:58 +0200 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: emacs-orgmode@gnu.org Cc: tsd@tsdye.com Thomas, >> Tom, do tell us more about what these habits are. > > The new exporter is really your friend. Where before I might choose to > generate a LaTeX block, now I look to generate Org output and then count > on the exporter to do the right thing on the way to pdf. > > The exporter's attribute system is very easy to use. The attributes you > need to access are always right there. > > I've also come to rely on filters quite a bit. I use them for > non-breaking spaces, the plus/minus symbol, and for the multiple > citation commands used by biblatex (e.g., \parencites). There seems to > be a move afoot to collect filters so they can be widely distributed. > I'd like to see the filters go to the Library of Babel, but for > reproducible research it is probably best to keep them with the source > document so there is no doubt about the fidelity of filter code. I too rely heavily on filters and customizations. I haven't been able to fully appreciate the asynchronous exporter yet. For instance I set some defaults for tables, pictures, add lots of entities etc. in my init file, and I went as far as writing a separate init file just loading just the org stuff. Now, this is clearly /not/ a very reproducible way of doing this. So I'm really interested in hearing or seeing implementation where the goal is reproducibility. On one hand I can appreciate keeping Org close to a vanilla state. On the other hand, I'd have to overwrite defaults every time (e.g. I /always/ want booktab tables). I guess I could keep an emacs-lisp block in the top of the file specifying stuff, but it also seems kind of tedious (copy-pasting every time). (Perhaps this could be resolved by loading external files hosted somewhere accessible). –Rasmus -- . . . The proofs are technical in nature and provides no real understanding.