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

From: Austin Frank <austin.frank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: configurable link export
Date: Fri, 19 May 2006 15:33:22 -0400	[thread overview]
Message-ID: <446E1D82.4060806@gmail.com> (raw)

First off, thank you to Carsten and David for org and org-publish. 
These tools have made it easier to get myself organized locally and 
online than it ever has been before.

I'd like to suggest a configuration option that influences the way links 
are exported in the org-export-as-* functions.

When I create local org files, I link to whatever files on my disk are 
relevant and useful.  When I publish those org files, some of the org 
links (like to other published org files) still work and make sense as 
html links.  Others (like links to local documents or directories) don't 
make any sense when published-- the resources they pointed to on the 
local system aren't on the remote filesystem that hosts the html pages.

To be more specific, I maintain a directory ~/notes/ and a directory 
~/blog/, each with a bunch of org files underneath it.  I then use 
org-publish to generate the html files, which are then uploaded to my 
website.  Crucially, this same directory structure is mirrored at my 
website, so local org links between those files work perfectly as html 
links when they are published and uploaded.

I'd love to be able to specify that I want all org links of 
[file:///home/aufrank/notes/*] and [file:///home/aufrank/blog/*] to be 
exported as full html links, and exclude org links to any other files on 
my filesystem at export time.

I think that David has established a good system for including and 
excluding files during publishing.  Org-publish first generates a list 
of files to publish based on regex matching of the extensions of files 
in a directory.  These are filtered through a regex-based exclude list, 
and then individual files can be added back in with an include list.

Applying this strategy to link export, I might want to have something 
like the following in my org-config.el:

(setq org-export-links-extension "org\\|txt"
       org-export-links-exclude   "~/*"
       org-export-links-include   ("~/notes/", "~/blog/"))

This would result in exporting all of the .org and .txt files in 
~/notes/ and ~/blog/ as working links in html files, but would ignore 
links in org files to anything else in my home directory during export.

There's certainly a question about how org links that are not exported 
as html links should be handled.  I would actually be fine with just 
exporting the double-bracketed notation, but I bet there are better 
ideas out there.

Thanks again for the org suite,
/au

next             reply	other threads:[~2006-05-19 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 19:33 Austin Frank [this message]
2006-05-20 11:01 ` configurable link export Carsten Dominik
2006-05-20 13:01   ` David O'Toole
2006-05-21 15:02     ` Austin Frank
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=446E1D82.4060806@gmail.com \
    --to=austin.frank@gmail.com \
    --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).