emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Berry, Charles" <ccberry@health.ucsd.edu>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: handling as special special block in derived export
Date: Wed, 19 Jan 2022 20:56:06 +0000	[thread overview]
Message-ID: <472D6327-20E1-460E-BB8F-043BD6D94B10@health.ucsd.edu> (raw)
In-Reply-To: <CAN_Dec_w-TzQCwct+LtNLO_Wj11OsGAcOA31Yy5ogB9ZpAzrXg@mail.gmail.com>

Matt,

> On Jan 19, 2022, at 5:52 AM, Matt Price <moptop99@gmail.com> wrote:
> 
> However, I'd really like to add a less verbose syntax, like this:
> 
> #+begin_r-stack :frag (appear appear)
> [[imglink1]]
> [[imglink2]]
> #+end_r-stack
> 
> My question is: will the exporter preserve information from these header-like arguments, and is 
> there a mechanism I can use in a custom ~special-block-function~ to make use of htem?
> 

Not as you have it there, but

#+header: :frag (appear appear)
#+begin_r-stack
[[imglink1]]
[[imglink2]]
#+end_r-stack


parses as 

(special-block
 (:type "r-stack" :begin 727 :end 815 :contents-begin 775 :contents-end 801 :post-blank 0 :post-affiliated 759 :header
	(":frag (appear appear)")
	:mode nil :granularity element :parent nil))

if that helps.

Chuck


  parent reply	other threads:[~2022-01-19 21:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 13:52 handling as special special block in derived export Matt Price
2022-01-19 17:18 ` John Kitchin
2022-01-20 15:21   ` Matt Price
2022-01-20 16:12     ` John Kitchin
2022-01-21  2:46       ` Matt Price
2022-01-19 20:56 ` Berry, Charles [this message]
2022-01-20 14:42   ` Matt Price

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=472D6327-20E1-460E-BB8F-043BD6D94B10@health.ucsd.edu \
    --to=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).