Make line numbers linkable when viewing files/annotate for hg.mozilla.org

RESOLVED FIXED

Status

--
enhancement
RESOLVED FIXED
11 years ago
4 years ago

People

(Reporter: Mardak, Assigned: Mardak)

Tracking

Details

(Whiteboard: [fixed in mercurial 1.0])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

11 years ago
Created attachment 279351 [details] [diff] [review]
v1

For "file" view on mercurial gitweb, has line numbers but they aren't links like on mxr. For "annotate" view, there are no line numbers at all.

Each line gets an anchor with id "l<num>" that links it itself.

Perhaps this should get pushed upstream?
(Assignee)

Comment 1

11 years ago
Created attachment 279402 [details] [diff] [review]
v2

Updated the patch to change the default template as well, so it's more likely to land upstream. So if that happens, this bug would be to grab those changes and run a crew/crew-stable version of mercurial on hg.mo.. ?

----

Add line anchors to file and annotate views for hgweb
http://www.selenic.com/pipermail/mercurial/2007-September/014491.html

This patch makes the line numbers into anchor tags with id "l<num>"
(e.g., l123) that link to itself with href=#l<num>. Updates default
and gitweb templates.

hgweb's ability to show the whole repository for any given changeset
is really useful, but referring to a particular line of a file such as
from a bug report would be nice. The patch adds a couple new
template-vars such as lineid and linenumber. Also, the annotate pages
didn't have line numbers to begin with, so there's a column for that
now.
Attachment #279351 - Attachment is obsolete: true
Assignee: server-ops → aravind
I do not want to maintain our own copy of mercurial builds, but would rather depend on this being present in the upstream builds.  I can change templates and such to customize the look, etc, but I'd rather not modify code that ships as a part of the app.

Could you please work with upstream devs to get this path there?
(Assignee)

Comment 3

11 years ago
I've submitted a patch to the mercurial-devel list

http://selenic.com/pipermail/mercurial-devel/2007-September/002806.html

It adds a couple new template vars for use on annotate, changeset, diff, file views. The patch also includes the changes for the map files themselves, but if those don't make it in upstream, we can apply those template changes ourselves.
Moving this to projects since I will work on this next quarter.
Component: Server Operations → Server Operations: Projects

Comment 5

11 years ago
Fixed upstream (http://www.selenic.com/mercurial/bts/issue506) and currently working great on hg.mozilla.org!

(Should be FIXED UPSTREAM, but I guess WORKSFORME is good enough.)
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
(Assignee)

Comment 6

11 years ago
Actually, I was trying to figure out how it got fixed and noticed that it seemed to be implemented exactly how I implemented it..

http://www.selenic.com/pipermail/mercurial/2007-September/014513.html

I sent in a patch some time ago back in September but never kept up to see if it ever got on. ;)

Apparently it did and made it for Mercurial 1.0. :)

http://hg.intevation.org/mercurial/crew/rev/800e2756c9ab
(Assignee)

Updated

11 years ago
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(Assignee)

Updated

11 years ago
Assignee: aravind → edilee
Status: REOPENED → NEW
(Assignee)

Updated

11 years ago
Status: NEW → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed in mercurial 1.0]
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.