emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Macro question
Date: Sun, 25 Oct 2015 10:45:50 +0100	[thread overview]
Message-ID: <CAFgFV9O=PhDau3gY+wLZw2y4ZE461-EBze616_JUmNCgXYydeQ@mail.gmail.com> (raw)
In-Reply-To: <87lhasyzcb.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

2015-10-24 19:02 GMT+02:00 Eric S Fraga <e.fraga@ucl.ac.uk>:

> On Saturday, 24 Oct 2015 at 13:37, Fabrice Popineau wrote:
>
> [...]
>
> > I find that using headers as in beamer is not pleasant (maybe that is
> just
> > me ?)
>
> Just to help you understand the positive aspect of headlines for
> structure in beamer, the use of headlines makes it incredibly easy to
> switch columns around, for instance, or to copy/move them from slide to
> slide.
>

You are right. This needs to be put forward.
In this case, the parameter that has to be made easily editable
is the width of the column. (Thinking about a common interface for
beamer and reveal)


> With respect to the HTML issue, what if you do not put blank lines
> between the different bits?  The blank lines are defining paragraphs, as
> far as I understand it.
>
>
It is possible to hack the reveal/html exporter.
Knowing that

{{{bFoo}}}
...
{{{eFoo}}}

gets exported to

<p>
<div class="foo">
</p>

<p>
</div>
</p>

The macros could be defined:
#+macro: bFoo @@html:</p><div class="foo"><p>@@
#+macro: eFoo @@html:</p></div><p>@@

and this way you get spurious paragraphs, but valid html
However, I'm not sure I want to follow this path !

Best regards,

Fabrice

[-- Attachment #2: Type: text/html, Size: 2380 bytes --]

  reply	other threads:[~2015-10-25  9:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 20:24 Macro question Fabrice Popineau
2015-10-23 20:37 ` Nicolas Goaziou
2015-10-23 21:33   ` Fabrice Popineau
2015-10-23 22:18     ` Nicolas Goaziou
2015-10-24  9:39       ` Fabrice Popineau
2015-10-24  9:53         ` Nicolas Goaziou
2015-10-24 11:37           ` Fabrice Popineau
2015-10-24 11:44             ` Nicolas Goaziou
2015-10-24 17:02             ` Eric S Fraga
2015-10-25  9:45               ` Fabrice Popineau [this message]
2015-10-25 12:04                 ` Eric S Fraga

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='CAFgFV9O=PhDau3gY+wLZw2y4ZE461-EBze616_JUmNCgXYydeQ@mail.gmail.com' \
    --to=fabrice.popineau@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).