From: Christoph LANGE <ch.lange@jacobs-university.de>
To: Samuel Wales <samologist@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: How to link to a fragment (aka anchor/bookmark) of a local file (e.g. a TiddlyWiki)?
Date: Fri, 11 Nov 2011 21:51:16 +0100 [thread overview]
Message-ID: <4EBD8AC4.5040203@googlemail.com> (raw)
In-Reply-To: <CAJcAo8tafTa4YqPKNyQ+JMW7xCVOWo9FY3WFHYrZGQcune6Ttw@mail.gmail.com>
Hi Samuel,
2011-11-11 21:30 Samuel Wales:
> I thought I had explained pretty clearly in the proposals that ID
> markers can be put in comments in the /external/ files.
Ah, OK, sorry, I didn't notice that. But, anyway, I'm not sure if I'd
want to put such markers into all pages of my TiddlyWiki. And while
that would still be _possible_, I'm sure that there is also a use case
for linking to fragments of local HTML files that you really don't want
to change or can't change. Imagine being a non-privileged user and
linking via file:///path/to/software/manual.html#feature to some section
of the manual of a software installed by an admin user, or to some
downloaded e-book or archived web page.
> Org IDs in external files -- which I propose to be in ID markers --
> are as unbreakable as you can arrange in a practical way.
BTW that reminds me of purple numbers
(http://en.wikipedia.org/wiki/Purple_Numbers), which I have seen in some
wikis. But they don't scale as well as your ID markers.
Cheers,
Christoph
--
Christoph Lange, http://www.facebook.com/ch.lange, Skype duke4701
prev parent reply other threads:[~2011-11-11 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:22 How to link to a fragment (aka anchor/bookmark) of a local file (e.g. a TiddlyWiki)? Christoph LANGE
2011-11-09 18:03 ` Samuel Wales
2011-11-11 20:06 ` Christoph LANGE
2011-11-11 20:30 ` Samuel Wales
2011-11-11 20:51 ` Christoph LANGE [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=4EBD8AC4.5040203@googlemail.com \
--to=ch.lange@jacobs-university.de \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).