emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dale Smith <dales@vxitech.com>
To: emacs-orgmode@gnu.org
Subject: Re: Customizable link types
Date: Mon, 25 Sep 2006 13:55:10 -0400	[thread overview]
Message-ID: <kplko7ompt.fsf@flexo.vxitech.com> (raw)
In-Reply-To: edd76422ae62f968c92c148a6b288a08@science.uva.nl

Carsten Dominik <dominik@science.uva.nl> writes:

> I am not using planner.el, so I can only guess how this feature is
> supposed to work.  Would you care to expand?

Sure.  I'm acually abusing interwiki links.  In my planner files, I
can quicky use "Bugzilla::1234" as a link to bug number 1234.  Planner
sees that as an interwiki link (the ::) .  Pressing return over the
link while in planner or following the link in the published html
actually goes to http://10.1.2.9/bugzilla/show_bug.cgi?id=1234

I *could* use something like
[[http://10.1.2.9/bugzilla/show_bug.cgi?id=1234][Bug# 1234]], but
that's a lot to type in.  Hmm.  It wouldn't be too hard to whip up
some elist that generates a link like that.

What I'm really asking is a way to extend the current list of link
types (gnus:, file:, vm:, etc.) with some user-defined types.


> On Sep 22, 2006, at 23:57, Dale Smith wrote:
>
>> I've been trying out org-mode instead of planner-el for a few weeks
>> now.  I like it.  However, there are a few things I miss.  One is
>> how easy it was to ad my own hyperlink types.  This was all I
>> needed to add Bugzilla::<number> links:
>>
>> (setq muse-wiki-interwiki-alist
>>       '(("Bugzilla" . "http://10.1.2.9/bugzilla/show_bug.cgi?id=")))

-Dale

-- 
Dale P. Smith
dales@vxitech.com
216-447-4059
216-447-8951 FAX

  reply	other threads:[~2006-09-25 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 21:57 Customizable link types Dale Smith
2006-09-25  7:01 ` Carsten Dominik
2006-09-25 17:55   ` Dale Smith [this message]
2006-09-25 18:29     ` Dale Smith
2006-09-26  5:48       ` Carsten Dominik
2006-09-25 18:48     ` 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:
  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=kplko7ompt.fsf@flexo.vxitech.com \
    --to=dales@vxitech.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
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).