From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Feature request for ox.el: add input-buffer attribute to INFO list Date: Sat, 02 Nov 2013 14:39:35 +0100 Message-ID: <87fvreudm0.fsf@gmail.com> References: <87txfvkm9u.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34451) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcbQG-000701-Fj for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 09:39:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcbQ8-0001ni-3E for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 09:39:28 -0400 Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:51494) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcbQ7-0001n7-Sg for emacs-orgmode@gnu.org; Sat, 02 Nov 2013 09:39:20 -0400 Received: by mail-we0-f176.google.com with SMTP id w62so528584wes.21 for ; Sat, 02 Nov 2013 06:39:18 -0700 (PDT) In-Reply-To: <87txfvkm9u.fsf@gmail.com> (Thorsten Jolitz's message of "Sat, 02 Nov 2013 13:42:37 +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: Thorsten Jolitz Cc: emacs-orgmode@gnu.org Hello, Thorsten Jolitz writes: > 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. I added :input-buffer to the communication channel. Regards, -- Nicolas Goaziou