From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Feature request for ox.el: add input-buffer attribute to INFO list Date: Sat, 02 Nov 2013 13:42:37 +0100 Message-ID: <87txfvkm9u.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52773) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcaXa-0000XT-QM for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 08:43:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcaXT-00020V-Hi for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 08:42:58 -0400 Received: from plane.gmane.org ([80.91.229.3]:60175) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcaXT-00020F-Af for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 08:42:51 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VcaXS-0002Xd-90 for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 13:42:50 +0100 Received: from e178188092.adsl.alicedsl.de ([85.178.188.92]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 Nov 2013 13:42:50 +0100 Received: from tjolitz by e178188092.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 Nov 2013 13:42:50 +0100 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 Hi List, in ox.el I find #+begin_src emacs-lisp (defun org-export--get-buffer-attributes () "Return properties related to buffer attributes, as a plist." ;; Store full path of input file name, or nil. For internal use. (list :input-file (buffer-file-name (buffer-base-buffer)))) #+end_src and consequently :input-file is nil if I export a buffer without an associated file (what I do quite often for some reason). Wouldn't it make sense to call this attribute :input-buffer-or-file or so and store 'full path of input file name' if there is an associated file, and the buffer name otherwise (instead of just nil)? Obviously, this extra information did not seem useful for the default use case of the Org exporter so it wasn't included in the communication channel. However, for other use cases it might be necessary to e.g. tag headlines with a unique ID of the original parse-tree they belonged to, and using the input-file (or input-buffer) name when creating this unique ID seems only logical. -- cheers, Thorsten