emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Custom entry IDs in HTML export
Date: Fri, 27 Mar 2009 13:57:58 -0400	[thread overview]
Message-ID: <87eiwiluft.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <6BF0FCBC-4343-4B8C-9A16-F4B9AC9B0F48@gmail.com> (Carsten Dominik's message of "Fri\, 27 Mar 2009 17\:16\:16 +0100")

Carsten Dominik <carsten.dominik@gmail.com> 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.


  reply	other threads:[~2009-03-27 17:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 12:47 Custom entry IDs in HTML export Daniel Clemente
2009-03-27 16:16 ` Carsten Dominik
2009-03-27 17:57   ` Bernt Hansen [this message]
2009-03-27 21:32     ` Sebastian Rose
2009-03-30 11:49       ` Daniel Clemente
2009-04-16  6:55         ` Carsten Dominik
2009-04-16  8:50           ` Sebastian Rose
2009-04-16 11:28             ` Carsten Dominik
2009-04-16 13:14               ` Sebastian Rose
2009-04-16 17:14                 ` Carsten Dominik
2009-04-16 20:50                   ` Sebastian Rose
2009-04-16 21:26                     ` Carsten Dominik
2009-04-16 22:37                       ` Sebastian Rose
2009-04-17  4:11                         ` Carsten Dominik

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:

  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=87eiwiluft.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).