From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Custom entry IDs in HTML export Date: Fri, 27 Mar 2009 13:57:58 -0400 Message-ID: <87eiwiluft.fsf@gollum.intra.norang.ca> References: <87myb7w2s9.fsf@CPU107.opentrends.net> <6BF0FCBC-4343-4B8C-9A16-F4B9AC9B0F48@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 1LnGJn-0005T4-MI for emacs-orgmode@gnu.org; Fri, 27 Mar 2009 13:58:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LnGJj-0005N6-Pn for emacs-orgmode@gnu.org; Fri, 27 Mar 2009 13:58:11 -0400 Received: from [199.232.76.173] (port=37247 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LnGJj-0005Mm-Fd for emacs-orgmode@gnu.org; Fri, 27 Mar 2009 13:58:07 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:56969) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LnGJj-0003fh-3B for emacs-orgmode@gnu.org; Fri, 27 Mar 2009 13:58:07 -0400 In-Reply-To: <6BF0FCBC-4343-4B8C-9A16-F4B9AC9B0F48@gmail.com> (Carsten Dominik's message of "Fri\, 27 Mar 2009 17\:16\:16 +0100") 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: Carsten Dominik Cc: org-mode mailing list Carsten Dominik writes: > I guess, with some work, we could reorganize the link storage > in a way that a user-given target of an ID become the preferred > hrefs and that section numbers will only be used when there is > not alternative..... > > hmmmm. How important is this.? I think it would be good to do eventually but it's not hugely important (to me). I've been living with the current behaviour for a long time. I post some of my task lists in HTML and paste a link to a task by navigating to it from the TOC. This allows other people to get directly to the target task but it is fragile and only works for a short period of time. If I change the structure of the tasks above the linked-to item (archive something to a different file, reorder tasks, etc) and export the document again then the old link now goes to the wrong place. It would be better to use a link that survives document restructuring instead. I've been too lazy to create manual links for my tasks -- I have tons of tasks and I might link to 3 or 4 of them in 6 months so I haven't bothered creating a manual link and re-exporting just for that. This workflow would however would fix the issue I'm having with it - and it's all supported right now -- except I have to write the link manually. If the link was used in the TOC instead of the standard link then I would just - create the link - export - go there from the TOC and paste the URL wherever I need it That would remove the error-prone step of creating the link manually when passing it along to someone else. Just my two cents. -Bernt