From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: export all linked images with a certain property or tag
Date: Tue, 02 Oct 2007 00:50:35 +0100 [thread overview]
Message-ID: <878x6mpf78.fsf@bzg.ath.cx> (raw)
In-Reply-To: <fdrehj$7mn$1@sea.gmane.org> (Fabian Braennstroem's message of "Mon, 01 Oct 2007 20:34:26 +0000")
Fabian Braennstroem <f.braennstroem@gmx.de> writes:
> Sounds good for me, maybe it would be good to add some kind off
> 'comment-region', which will not be exported by default.
Org already knows about comments. You can comment entire regions by
selecting them, then pressing M-;. Whenever asked, enter "#" as the
comment character.
Within comments, all links are still active (even if the fontification
is quite misleading on this). So you should be able to insert pictures
and jump to them as usual.
Both HTML and LaTeX exporters will just skip comments.
See (info "(org)Comment lines")
> Another and maybe easier way for the export could be to define the
> number of levels of a searched tag; then I would reorganize my
> structure a bit:
The export engine is already aware of levels in some ways.
`org-export-headline-levels' (or the "H:" option in #+OPTIONS) sets the
level of headlines to export. For the HTML exporter, levels below this
one are exported as list items. The LaTeX exporter comes with another
option: `org-export-latex-low-levels' which decides what to do with
lower levels: you can either convert them as descriptive lists, skip
them or use your own syntax. AFAIK there is no equivalent for HTML,
but this would do what you request.
HTH,
--
Bastien
next prev parent reply other threads:[~2007-10-01 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 18:36 export all linked images with a certain property or tag Fabian Braennstroem
2007-10-01 17:05 ` Bastien
2007-10-01 20:34 ` Fabian Braennstroem
2007-10-01 23:50 ` Bastien [this message]
2007-10-02 21:19 ` Fabian Braennstroem
2007-10-02 22:47 ` Bastien
2007-10-03 10:30 ` Fabian Braennstroem
2007-10-03 12:24 ` Bastien
2007-10-03 17:01 ` Fabian Braennstroem
2007-10-03 18:11 ` Fabian Braennstroem
2007-10-03 16:29 ` Bastien
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=878x6mpf78.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).