From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request for ox.el: add input-buffer attribute to INFO list
Date: Sat, 02 Nov 2013 14:39:35 +0100 [thread overview]
Message-ID: <87fvreudm0.fsf@gmail.com> (raw)
In-Reply-To: <87txfvkm9u.fsf@gmail.com> (Thorsten Jolitz's message of "Sat, 02 Nov 2013 13:42:37 +0100")
Hello,
Thorsten Jolitz <tjolitz@gmail.com> 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
next prev parent reply other threads:[~2013-11-02 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 12:42 Feature request for ox.el: add input-buffer attribute to INFO list Thorsten Jolitz
2013-11-02 13:39 ` Nicolas Goaziou [this message]
2013-11-02 14:04 ` Thorsten Jolitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvreudm0.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.