Ãscar Fuentes <address@hidden> writes:
> Wes Hardaker <address@hidden> 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.
More generally, using Org as a front-end for other bug tracking online
tools looks more actionnable than using it as a back-end.
> 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.
Aren't those ids always hidden, either within a link or within a drawer?
> 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.
I think it's already the case.
--
Bastien
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4