The one issue that comes to mind is the line number changes, and as the codex is already a moving target, I'm not sure how much we want to add that over head....
On Nov 9, 2011, at 1:04 AM, Michael Beckwith <[email protected]> wrote: > I was wondering if it were feasible to link to the specific line where a > function is declared when saying "foo function is located in > wp-includes/bar.php". Instead of just linking to > http://core.trac.wordpress.org/browser/tags/3.2.1/wp-includes/bar.php, go to > the actual destination, and then copy/paste in the link + line number. > > For example from get_userdata(): > > Current source link = > http://core.trac.wordpress.org/browser/tags/3.2.1/wp-includes/pluggable.php > Proposed source link = > http://core.trac.wordpress.org/browser/tags/3.2.1/wp-includes/pluggable.php#L94 > > > The #L94 anchor pulls them straight to the start of the comment block for the > function. > > Thoughts? Issues that I wasn't around for the first time someone thought this > up? > _______________________________________________ > wp-docs mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-docs
_______________________________________________ wp-docs mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-docs
