From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joon Ro Subject: Re: Questions about using macro replacement Date: Sat, 26 Aug 2017 23:56:26 +0000 Message-ID: References: , Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_BY2PR15MB042112C787E69A87D46F2532EB980BY2PR15MB0421namp_" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42943) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlkwK-0002qS-32 for emacs-orgmode@gnu.org; Sat, 26 Aug 2017 19:56:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlkwH-00089t-0J for emacs-orgmode@gnu.org; Sat, 26 Aug 2017 19:56:32 -0400 Received: from mail-oln040092001038.outbound.protection.outlook.com ([40.92.1.38]:10160 helo=NAM01-BY2-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dlkwG-00089M-Go for emacs-orgmode@gnu.org; Sat, 26 Aug 2017 19:56:28 -0400 In-Reply-To: Content-Language: en-US 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" To: Matt Price Cc: "emacs-orgmode@gnu.org" --_000_BY2PR15MB042112C787E69A87D46F2532EB980BY2PR15MB0421namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Answering without full knowledge! Thank you so much for the reply - your reply gave me several ideas. I think= Q1 and Q3 are solved, but I still have no idea how to do Q2 or if it is po= ssible. Q1, I figured it out and started using it - the {{{n}}} macros are awesome! 2. I was wondering if it is possible use macro expansion for :EXPORT_FILE_N= AME: property of a subtree? Since macros can be set to expand to arbitrary elisp, I would think this *s= hould* be possible. I forget the syntax but something like: #+MACRO: efn (eval (get-export-file-name)) #+BEGIN_SRC emacs-lisp (defun get-export-file-name () (org-element-property :export-file-name (org-element--current-element) )) #+END_SRC * some heading :PROPERTIES :EXPORT_FILE_NAME: test-me :END: will get you somewhat close. I don't understand the org-element api very w= ell though and it generally takes me a few tries to get this sort of thing = right. With this one, I was actually looking for using macros inside :EXPORT_FILE_= NAME: property. Ultimately what I want to do is: * some heading :PROPERTIES: :EXPORT_FILE_NAME: {{{n('class',1)}}} test-me :END: However, it did not work, as the file name became literal {{{n('class',1)}}= } test-me.pdf. 3. Is it possible to create a file link which uses macro? I would like to c= reate a link to the exported pdf file dynamically. For example, if the valu= e of :EXPORT_FILE_NAME: is exported, how would I create a link which automa= tically link to exported.pdf? I don't think a macro will do this for you since, if I understand correctly= , macros are not aware of the export target. So probably you would need so= me other mechanism to od this. I figured it out using elisp link: elisp:(org-open-link-from-string (concat "file:./" (org-entry-get nil "EXPO= RT_FILE_NAME") ".pdf")) Best Regards, Joon --_000_BY2PR15MB042112C787E69A87D46F2532EB980BY2PR15MB0421namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Answering without full knowledge!

Thank you so much for the reply - your repl= y gave me several ideas. I think Q1 and Q3 are solved, but I still have no = idea how to do Q2 or if it is possible.


Q1, I figured it out and started using it - the = {{{n}}} macros are awesome!

2. I was wondering if it is possible use macro expansion for :EXPORT_F= ILE_NAME: property of a subtree?
Since macros can be set to expand to arbitrary elisp, I would think th= is *should* be possible.  I forget the syntax but something like:

#+MACRO: efn (eval (get-export-file-name))

#+BEGIN_SRC emacs-lisp
(defun get-export-file-name ()
 (org-element-property :export-file-name (org-element--current-el= ement) ))
#+END_SRC

* some heading
:PROPERTIES
:EXPORT_FILE_NAME: test-me
:END:

will get you somewhat close.  I don't understand the org-element = api very well though and it generally takes me a few tries to get this sort= of thing right.


With this one, I was actually looking for using macros inside :EXPORT_FILE_= NAME: property. Ultimately what I want to do is:

* some heading
:PROPERTIES:
:EXPORT_FILE_NAME: {{{n('class',1)}}} test-me
:END:

However, it did not work, as the file name became literal {{{n('class',1)}}} test-me.pdf.



3. Is it possible to create a file link which uses macro? I would like to c= reate a link to the exported pdf file dynamically. For example, if the value of :EXPORT_FILE_NAME: is exported, how would I create a link= which automatically link to exported.pdf?

I don't think a macro will do this for you since, if I understand corr= ectly, macros are not aware of the export target.  So probably you wou= ld need some other mechanism to od this. 

I figured it out using elisp link:

elisp:(org-open-link-from-string (concat "file:./" (org-entr= y-get nil "EXPORT_FILE_NAME") ".pdf"))

Best Regards,
Joon
--_000_BY2PR15MB042112C787E69A87D46F2532EB980BY2PR15MB0421namp_--