From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: IDs Date: Wed, 22 Apr 2009 23:13:06 -0400 Message-ID: <87ab68ukot.fsf@gollum.intra.norang.ca> References: <49EFD1F6.6090504@gmail.com> 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 1LwpNC-000287-Oa for emacs-orgmode@gnu.org; Wed, 22 Apr 2009 23:13:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LwpN8-00027j-Iq for emacs-orgmode@gnu.org; Wed, 22 Apr 2009 23:13:14 -0400 Received: from [199.232.76.173] (port=60555 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LwpN8-00027f-E8 for emacs-orgmode@gnu.org; Wed, 22 Apr 2009 23:13:10 -0400 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:57395) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LwpN8-0007Um-4D for emacs-orgmode@gnu.org; Wed, 22 Apr 2009 23:13:10 -0400 In-Reply-To: <49EFD1F6.6090504@gmail.com> (srandby@gmail.com's message of "Wed\, 22 Apr 2009 22\:27\:02 -0400") 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: srandby@gmail.com Cc: "[Orgmode]" srandby@gmail.com writes: > I saw some discussion on the list about custom IDs, but it confused > me. So, here is my problem. > > I upgraded to 6.26. Now, when I export my index.org file to html, the > headlineline > > * Courses > > is exported to > >
>

Courses

>
> > instead of > >
>

Courses

>
. This was a bug in the 6.26 release that was fixed in 6.26a > > This happens for all other headlines in index.org too. > > I don't want to define a custom ID for every headline, I want org-mode > to generate them automatically as it did in the past. For now, I've > gone back to 6.25b. > > I see that 6.26d is out. I haven't tried it yet. Is this issue > resolved in 6.26d, or is the new way the default. If so, how do I make > things work the old way? 6.26d should work fine. Yes it is resolved. -Bernt