On Fri, Jun 6, 2014 at 6:12 PM, Scott Robison <sc...@casaderobison.com>
wrote:

> I don't think this is currently possible, but I've been wrong before, so
> let me ask: I know it is possible to link to individual artifacts by ID
> which displays the source, but is it possible to link to a given line
> number (range) within a given artifact, perhaps highlighting it in the
> process?
>

You mean like this:
http://www.fossil-scm.org/fossil/artifact/6eb26bb7a6?ln=1755-1759

(Note that the highlighted code is in fact the code that implements the
"ln=" query parameter that does the range highlighting.  A kind of semantic
recursion.)


>
> My reason for asking: I've been given a new assignment by my employer to
> learn / understand some relatively obscure source code written by a former
> employee. This is proprietary code that can't be shared outside the
> company, but it is not documented (by which I mean there are comments
> through the code, but no real design or high level understanding of *why*
> it does *what* it does).
>
> My thoughts on how to handle this task (where code is currently stored in
> an svn repo and will be migrated in the not too distant future to git) is
> to take the current code and import it into a fossil repo, then use the
> wiki / inline documentation features to describe it in detail. Part of what
> I would like to do in the documentation is link to individual lines or
> blocks in the individual source files so that the reference is internally
> complete so that I don't have to keep separate source & documentation files
> in sync.
>
> Thanks in advance for your help!
>
> --
> Scott Robison
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>


-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to