From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yu Subject: Variable settings in .emacs VS cross device portability. Date: Mon, 30 Jan 2012 17:13:09 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:46294) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RrtrX-0005Mi-2Z for emacs-orgmode@gnu.org; Mon, 30 Jan 2012 11:13:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RrtrS-0002fU-1q for emacs-orgmode@gnu.org; Mon, 30 Jan 2012 11:13:47 -0500 Received: from mailout-de.gmx.net ([213.165.64.23]:41282) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RrtrR-0002ew-MC for emacs-orgmode@gnu.org; Mon, 30 Jan 2012 11:13:42 -0500 Received: by lagj5 with SMTP id j5so625692lag.0 for ; Mon, 30 Jan 2012 08:13:39 -0800 (PST) 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: org-mode mailing list Hello! I was wondering if there is a possibility to make org-files fully portable in behaviour (especially when exporting) between different emacs installations. When reading the mailing list or other writing about org-mode, commonly suggestions of the type "just add (setq org-foo bar) to your .emacs". This however creates a dependency on the local setup of the variables, which likely will be a problem, when sharing the file with someone. My current solution is to use a template file with #+BIND: and #+PROPERTY: lines in a setup section rather than setting anything in configuration files. However, is there some way to turn a user-variable dependent file into a portable file? I was thinking of something along the lines of "dumping user-specified variables into a list of #+BIND lines" and, if necessary, the magic "-*- var: value -*-" line at the start of the file (or, less elegant because of spreading options across different positions in the file) the commented "local variables" structure near the end of the file. The latter two variants only apply if I am right about #+BIND lines applying only during export (whereas the magic emacs lines should create buffer-local bindings). king regards, Yu