From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: HTML export and heading levels Date: Wed, 16 Jan 2008 02:42:28 +0000 Message-ID: <87hchewkx7.fsf@bzg.ath.cx> References: <87wsqaplsp.fsf@gollum.intra.norang.ca> 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 1JEyEd-0000QH-Hr for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 21:42:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JEyEb-0000Of-Ti for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 21:42:35 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JEyEb-0000OW-Np for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 21:42:33 -0500 Received: from fg-out-1718.google.com ([72.14.220.152]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JEyEb-0003zd-T1 for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 21:42:34 -0500 Received: by fg-out-1718.google.com with SMTP id d23so92684fga.30 for ; Tue, 15 Jan 2008 18:42:32 -0800 (PST) In-Reply-To: <87wsqaplsp.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Tue, 15 Jan 2008 21:05:26 -0500") 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 Hi Bernt, thanks for sharing this -- I add some (hopefully useful) comments. Bernt Hansen writes: > I started playing with HTML export this week and since I'm lazy I don't > want to have to remember to export. I created a few simple functions > that export my org file to HTML and copies the resulting HTML file to my > webserver when I save my org file using C-x C-s. I guess we need the /home/bernt/bin/publish file for this to be really reusable, no? Another way to do a similar think (add-hook 'org-mode-hook (lambda() (add-hook 'before-save-hook 'org-publish-current-file t t))) This will run the `org-publish-current-file' function each time you try to save an org-mode buffer. For this to take effect, the file has to be part of a project -- see the manual (info "(org)Configuration") on how to configure a project. > (add-hook 'text-mode-hook 'bth-org-define-keys) I guess this should be: (add-hook 'org-mode-hook 'bth-org-define-keys) > Now I have multiple org-mode files and they don't all have the same > structure. I've hardcoded the HTML export to level 2 in > bth-export-save-then-publish but it would be much better to have the > export honour the org-mode file option instead. You can configure this through the org-publish project parameters. See the manual: (info "(org)Publishing options") and look for the :headline-levels parameter. > One other thing that would be handy is a way to skip tasks in the > export. I'm not sure if anything like that exists yet or not. (I wish we could set complex filters when exporting, but that may be another story...) > I normally have a > > * Timelog > > entry at the top of every org file which has the clock table format that > is appropriate for that file. I really don't want that included in my > export to HTML so it would be great if there was a way to say 'skip this > heading and all sublevel headings' on export - maybe as a property or > something. For this you can use this workaround: * COMMENT Timelog HTH, -- Bastien