emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Chris Gray <chrismgray@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Bug: LaTeX export and LaTeX environment
Date: Tue, 1 Jun 2010 16:46:13 +0200	[thread overview]
Message-ID: <4BAF43C3-C370-4134-A3BE-B3F0D4EF98BB@gmail.com> (raw)
In-Reply-To: <86y6eyyhwo.fsf@portan.ibr.cs.tu-bs.de>


On Jun 1, 2010, at 3:57 PM, Chris Gray wrote:

> Carsten Dominik wrote:
>
>> Hi Mark,
>
>> several environments already to accept parameters, and in all cases  
>> it
>> is
>> done by just listing the arguments after the begin statement,
>> separated by spaces.
>
>> So what you could implement is that if a user writes
>
>> #+begin_xxx {aa}[bb]{cc}
>
>> that org-special-blocks will then create
>
>> \begin{xxx}{aa}[bb]{cc}
>
>> I think we must ask for the space, to make sure that all old code  
>> will
>> work.
>> A patch to org-special-blocks for this goal would be very useful, I
>> think.
>
> Hi Carsten,
>
> I actually needed this yesterday, so I'll make a patch and try to send
> it in the next couple of days.
>
> Should anything be done for the HTML exporter if there are arguments?

Hi Chris

I can't think of anything useful - unless we do something like

#+begin_xxx -largs "{aa}[bb]{cc}" -hargs "aa=\"xxx\" bb=\"uuu\""

and then use the largs for LaTeX and the hargs as additional attributes
in the HTML div.

But right now I don't see many applications for this in HTML, so
I am not sure it is worth the trouble.  Maybe just ignore these  
additional
arguments, or put them as a string into some special attribute like

<div class="xxx" latex_block_args="{aa}[bb]{cc}">

so that some javascript hacker can do something with these
arguments.

I am not sure what the right cause of action is, and I would
be happy already with a patch that attaches the rest of the line
in LaTeX and throws it away in HTML.

I am starting to think we should have this package in the
core - can I get you to sign the papers with the FSF for
your contributions to Org-mode?  Instructions are here:

http://orgmode.org/worg/org-contribute.php

Cheers

- Carsten

  reply	other threads:[~2010-06-01 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19  6:34 Bug: LaTeX export and LaTeX environment Ulf Stegemann
2010-05-19  6:57 ` Carsten Dominik
2010-05-19  7:27   ` Ulf Stegemann
2010-05-19 19:20     ` Mark Elston
2010-06-01 13:42       ` Carsten Dominik
2010-06-01 13:57         ` Chris Gray
2010-06-01 14:46           ` Carsten Dominik [this message]
2010-06-01 15:02           ` Chris Gray
2010-06-01 21:20             ` Mark Elston
2010-06-02  8:28               ` Chris Gray

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=4BAF43C3-C370-4134-A3BE-B3F0D4EF98BB@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=chrismgray@gmail.com \
    --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).