From: Carsten Dominik <dominik@science.uva.nl>
To: Alex Fu <alexfu@arcor.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 4.68
Date: Tue, 20 Mar 2007 13:14:17 +0100 [thread overview]
Message-ID: <e65fb0eaac01e71f4a53b88ac72c25df@science.uva.nl> (raw)
In-Reply-To: <op.tpfwtz1c1wjnvxafu@pc3>
On Mar 19, 2007, at 15:21, Alex Fu wrote:
> Dear all,
>
> On Fri, 16 Mar 2007 13:08:33 -0400, Carsten Dominik
> <dominik@science.uva.nl> wrote:
>
>>> * Exporting text before the first heading ?
>>>
>>> It seems that text before the first heading is not exported. Using
>>> #+TEXT: might help, but #+TEXT: does not understand links. Is that
>>> intentional ?
>>
>> I guess this is not very well though-out, and maybe it would be good
>> to simply export the text before the first heading.
>> That TEXT is not HTML processed I would also consider as
>> a bug, but I know that some have made clever use of this bug
>> to insert custom HTML into a file. This is now no loger
>> necessary since you can embed protected HTML with special commands.
>
> Note that the #+HTML: and #+BEGIN_HTML...#+END_HTML directives are not
> (yet) a replacement for inserting literal html as it can be done using
> #+TEXT:. As far as I've noticed, #+TEXT: inserts html (or any other
> text) before the first heading (before the <h2> in the resulting html
> file), something the #+HTML directives can't do, since the effect of
> placing it before the first heading is null, as it is not exported.
This will change. In the future, #+TEXT: lines will be fully
processed like any other buffer line, I consider that fact that
is was not processed so far as a bug. On the other hand,
constructs like the following will be allowed:
#+TEXT: Processed text iwth *bold* words
#+TEXT: #+BEGIN_HTML
#+TEXT: <a href="...">unprocessed HTML code</a>
#+TEXT: #+END_HTML
#+TEXT: /This/ will be processed again
There will also be an option to export the text before the
first headline, in which case the #+TEXT prefix is not necessary.
- Carsten
next prev parent reply other threads:[~2007-03-20 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 4:31 Org-mode version 4.68 Carsten Dominik
2007-03-16 11:11 ` Bastien
2007-03-16 17:08 ` Carsten Dominik
2007-03-16 18:39 ` Bastien
2007-03-18 7:00 ` Carsten Dominik
2007-03-17 11:38 ` David O'Toole
2007-03-31 21:58 ` T. V. Raman
2007-05-21 6:36 ` Carsten Dominik
2007-03-19 14:21 ` Alex Fu
2007-03-20 12:14 ` Carsten Dominik [this message]
2007-03-21 6:59 ` Carsten Dominik
2007-03-21 8:58 ` Bastien
2007-03-22 8:25 ` Leo
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=e65fb0eaac01e71f4a53b88ac72c25df@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=alexfu@arcor.de \
--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).