From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: export all linked images with a certain property or tag Date: Tue, 02 Oct 2007 00:50:35 +0100 Message-ID: <878x6mpf78.fsf@bzg.ath.cx> References: <87sl4ug3z3.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IcV2H-000347-8G for emacs-orgmode@gnu.org; Mon, 01 Oct 2007 19:50:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IcV2A-0002si-Qv for emacs-orgmode@gnu.org; Mon, 01 Oct 2007 19:50:47 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IcV2A-0002sP-NM for emacs-orgmode@gnu.org; Mon, 01 Oct 2007 19:50:42 -0400 Received: from wx-out-0506.google.com ([66.249.82.239]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IcV2A-0004Le-8w for emacs-orgmode@gnu.org; Mon, 01 Oct 2007 19:50:42 -0400 Received: by wx-out-0506.google.com with SMTP id s7so3214195wxc for ; Mon, 01 Oct 2007 16:50:41 -0700 (PDT) In-Reply-To: (Fabian Braennstroem's message of "Mon, 01 Oct 2007 20:34:26 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Fabian Braennstroem 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