From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Customizable link types Date: Mon, 25 Sep 2006 20:48:48 +0200 Message-ID: <00a669a897c5654f701293274a4f9ab5@science.uva.nl> References: Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GRvVc-00064r-NC for emacs-orgmode@gnu.org; Mon, 25 Sep 2006 14:48:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GRvVb-00063u-1e for emacs-orgmode@gnu.org; Mon, 25 Sep 2006 14:48:52 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GRvVa-00063X-Tr for emacs-orgmode@gnu.org; Mon, 25 Sep 2006 14:48:50 -0400 Received: from [194.134.35.149] (helo=smtp08.wanadoo.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GRva3-00084T-N9 for emacs-orgmode@gnu.org; Mon, 25 Sep 2006 14:53:27 -0400 Received: from [192.168.2.2] (dc5146d3e6.adsl.wanadoo.nl [81.70.211.230]) by smtp8.wanadoo.nl (Postfix) with ESMTP id B08B0253CF for ; Mon, 25 Sep 2006 20:48:49 +0200 (CEST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Hi Dale, thanks for the extra information. Seems to me that there are really two issues here. One is the idea you point out with the bugzilla example. I would like to call this "link abbreviations". I like the idea and think it could be used in many ways. It might also be useful to allow setting such abbreviations on a per-file base with lines like #+LINKABBREV: Bugzilla "http://10.1.2.9/bugzilla/show_bug.cgi?id=" The second issue you are mentioning is an extensible link system like muse has it, where new link types like gnus, vm and other can be defined and hooked into the the system. The muse system is of an admirable generality, but so far I have chosen not to follow the same road, because (at least in planner, I don't know about muse itself) the generality forces you to put a long list of require statements into .emacs before the system will function properly even for the standard cases most people need. A system which just has all important types built-in and active seems more user-frienly (though less hacker-friendly) to me. - Carsten On Sep 25, 2006, at 19:55, Dale Smith wrote: > Carsten Dominik 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:: links: >>> >>> (setq muse-wiki-interwiki-alist >>> '(("Bugzilla" . "http://10.1.2.9/bugzilla/show_bug.cgi?id="))) > > -Dale >