From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-orgmode@gnu.org
Subject: Re: OrgmodeOrg-mode as a bug tracker.
Date: Tue, 21 Jul 2009 01:48:34 +0200 [thread overview]
Message-ID: <87zlay6hm5.fsf@telefonica.net> (raw)
In-Reply-To: sdws632axa.fsf@wes.hardakers.net
Wes Hardaker <wjhns209@hardakers.net> writes:
> o> The only downside is the lack of a referenced wiki system: simple links
> o> to revisions (r1010) tickets (#245) etc.
>
> You can actually get around this somewhat if you're linking to, say, a
> svn web server. I do this using something like this:
>
> (setq org-link-abbrev-alist
> '(
> ("nsb"
> . "http://sourceforge.net/tracker/index.php?func=detail&group_id=12694&atid=112694&aid=%s")))
>
> Thus any links like [[nsb:1234]] will link to the right web page for bug
> #1234 in the Net-SNMP bug database. SVN repo pointers, etc, can be done
> just as easily.
I was thinking along this lines for implementing links to subversion
revisions. However, links to bugs reports are not so easy, because you
must explicitly assign a unique id to each TODO. org-id.el is not very
human-friendly as it generates long ids.
I guess it is possible to fix this with some lisp customizations. Once
the automatic generation and insertion of a simple (counter-based)
unique id for each new TODO is achieved, linking to bugs becomes easy
using the mechanism you mentioned above.
--
Óscar
next prev parent reply other threads:[~2009-07-20 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 15:34 Org-mode as a bug tracker Óscar Fuentes
2009-07-17 16:25 ` Óscar Fuentes
2009-07-17 17:58 ` Eric S Fraga
2009-07-17 18:35 ` Matthew Lundin
2009-07-17 19:02 ` Eric S Fraga
2009-07-18 10:46 ` Bastien
2009-07-19 21:12 ` Óscar Fuentes
2009-07-20 6:18 ` Bastien
2009-07-20 14:15 ` JBash
2009-07-20 14:35 ` Óscar Fuentes
2009-07-18 10:46 ` Bastien
2009-07-20 23:26 ` OrgmodeOrg-mode " Wes Hardaker
2009-07-20 23:48 ` Óscar Fuentes [this message]
2009-07-21 6:01 ` Bastien
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=87zlay6hm5.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).