emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] e-latex back-end: changes to attributes syntax
Date: Wed, 28 Nov 2012 16:23:14 +0100	[thread overview]
Message-ID: <87ip8p92fx.fsf@gmail.com> (raw)
In-Reply-To: <20121128132735.GA5988@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Wed, 28 Nov 2012 14:27:35 +0100")

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> Personally I think having the option to shoot myself in the foot is
> preferable over not being able to configure.  But then others may not
> agree.  Is it possible to disallow :overlay when :environment is
> provided?  If so you could generate a warning during export.
>
> That said, the way I see it, most widely used list-like environments are
> of the "new item on a new line" kind (which are supported by overlays).
> I wanted to use inparaenum for ease of editing, in my slide I wanted an
> inline list (where overlays aren't really needed).  So setting the two
> attributes simultaneously is probably very unlikely.
>
> I am quoting my use case below in case that helps the discussion.
> Something like item (1) would have been nice, however I ended up using
> (2).
>
>
>   1) Asymmetries can be constructed that are,
>      #+attr_beamer: :environment "inparaenum" :options "i)"
>      1. CP-odd,
>      2. CPT-odd and
>      3. T-odd
>
>   2) Asymmetries can be constructed that are, i) CP-odd, ii) CPT-odd and
>      iii) T-odd.

Case 1 should now be supported.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2012-11-28 15:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 16:35 [ANN] e-latex back-end: changes to attributes syntax Nicolas Goaziou
2012-11-21 17:40 ` Rasmus
2012-11-21 18:00   ` Nicolas Goaziou
2012-11-25 15:31   ` Nicolas Goaziou
2012-11-25 16:41     ` Rasmus
2012-11-22 16:29 ` Alan Schmitt
2012-11-22 16:48   ` Nicolas Goaziou
2012-11-22 19:02     ` Alan Schmitt
2012-11-22 23:02 ` Thomas S. Dye
2012-11-25 15:24   ` Nicolas Goaziou
2012-11-25 18:13     ` Thomas S. Dye
2012-11-23  9:00 ` Alan Schmitt
2012-11-23 11:59   ` Nicolas Goaziou
2012-11-23 12:37     ` Alan Schmitt
2012-11-23 12:59       ` Nicolas Goaziou
2012-11-23 13:13       ` Giovanni Ridolfi
2012-11-23 13:42       ` Gregor Zattler
2012-11-26  0:39 ` [ANN] " Suvayu Ali
2012-11-28 12:58   ` Nicolas Goaziou
2012-11-28 13:27     ` Suvayu Ali
2012-11-28 15:23       ` Nicolas Goaziou [this message]

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=87ip8p92fx.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@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).