emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: Extending the Org syntax by a custom exporter - how to do it?
Date: Mon, 17 Mar 2014 16:43:47 +0100	[thread overview]
Message-ID: <20140317164347.317c2259@aga-netbook> (raw)
In-Reply-To: <87mwgqqlk1.fsf@gmail.com>

Dnia 2014-03-16, o godz. 15:12:46
Nicolas Goaziou <n.goaziou@gmail.com> napisał(a):

> Marcin Borkowski <mbork@amu.edu.pl> writes:
> 
> > So basically I can attach #+ATTR_WHATEVER attributes also to lists,
> > paragraphs and other elements?  Even list items?  (This would mean
> > that I could mark the "correct" answer using that syntax - but I
> > think this would be too verbose.  I can't see any harm in abusing
> > checkboxes for that, though I [[http://xkcd.com/292/][might be
> > mistaken]];))
> 
> You can attach attributes (which is a subset of "affiliated keywords"
> category) to any element excepted clock, headline, inlinetask, item,
> planning, node-property, section and table-row types.

I see.

> So, plain lists can have attributes, but not items. There are
> workarounds, though. For example, you can use an export snippet at the
> beginning of the item to mark the correct answer. Hence, assuming
> "qcm" is the name of your backend, you could use:
> 
>   #+attr_qcm: :type mct
>   - answer a
>   - @@qcm:correct@@ answer b
>   - answer c
> 
> "ox-beamer.el" uses it to specify action overlays item wise. See
> `org-beamer-item' for an example.

Interesting, though I think I'll stick with checkboxes - esepcially
that it is easy for the user/author to mark them on and off.

> Regards,

Thanks again!

-- 
Marcin Borkowski
room B3-46, phone no +48 61 829 5375
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

  reply	other threads:[~2014-03-17 15:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 10:10 Extending the Org syntax by a custom exporter - how to do it? Marcin Borkowski
2014-03-15 11:10 ` John Kitchin
2014-03-15 11:25   ` Marcin Borkowski
2014-03-15 11:29     ` Marcin Borkowski
2014-03-15 21:22 ` Marcin Borkowski
2014-03-16 10:16   ` Nicolas Goaziou
2014-03-16 11:18     ` Marcin Borkowski
2014-03-16 11:57       ` Nicolas Goaziou
2014-03-16 13:33         ` Marcin Borkowski
2014-03-16 14:12           ` Nicolas Goaziou
2014-03-17 15:43             ` Marcin Borkowski [this message]
2014-03-16 16:05         ` Aaron Ecay
2014-03-17 16:31     ` Marcin Borkowski
2014-03-22 11:23       ` Nicolas Goaziou
2014-11-25 21:25     ` Marcin Borkowski
2014-11-25 21:46       ` Marcin Borkowski
2014-11-26  2:46       ` John Kitchin
2014-11-26 14:23         ` John Kitchin
2014-11-26 11:59       ` Nicolas Goaziou

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=20140317164347.317c2259@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --cc=emacs-orgmode@gnu.org \
    /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).