emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Austin Frank <austin.frank@gmail.com>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: configurable link export
Date: Sun, 21 May 2006 11:02:13 -0400	[thread overview]
Message-ID: <447080F5.1020700@gmail.com> (raw)
In-Reply-To: <m3psi8alyz.fsf@gnu.org>

David O'Toole wrote:
> All we need is for people to specify a property called :link-base that
> is the prefix for a URL. For example, if :publishing-directory is
> "/ssh:user@host:~/public_html/images", the user should probably set
> the :link-base to "/images" or "http://foosite.org/images"

This will definitely work for linking between projects.  But not all of
my links in a given org file are to files in projects.  If I have a link
[[file:///home/aufrank/my_movie.mpg][movie I made]], and that movie is
not part of a project, and there is no chance I am ever going to upload
that movie to my webserver, then I don't really want the link to be
published as <link-base>/my_movie.mpg.  I want to have a way to say "you
know what, don't bother trying to make this into a hyperlink.  I already
know it won't work as one."

> Given this one extra piece of information, then it is a simple matter
> for the :link-transform function to actually generate proper URLs
> (instead of simply validating them.) This would free projects from the
> requirement that the web server must have the exact same directory
> layout as your local project files.

This makes sense, and I would love to see it implemented.  But I'm still
not sure it addressed the problem described above.  If it does and I'm
just not getting it, please explain :)

> This would allow, as you say, for link targets to be validated and
> transformed automatically, given just the structure and contents of
> org-publish-project-alist.

Again, ideal for publishing projects and the links between them, but
does not address how to handle links to non-project local files.  My
vote is to export them as bracketed text, just as they're written in the
raw org file, but the really important thing is that they _not_ be
exported as hyperlinks if I tell org ahead of time that they're
guaranteed to be dead-on-upload.

Thanks,
/au

next prev parent reply	other threads:[~2006-05-21 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 19:33 configurable link export Austin Frank
2006-05-20 11:01 ` Carsten Dominik
2006-05-20 13:01   ` David O'Toole
2006-05-21 15:02     ` Austin Frank [this message]
2006-05-22  9:22     ` Carsten Dominik
2006-05-21 15:02   ` Austin Frank

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=447080F5.1020700@gmail.com \
    --to=austin.frank@gmail.com \
    --cc=dto@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /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

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