Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: Coverage tool visibility within emacs

by pvaldes (Chaplain)
on May 26, 2012 at 00:17 UTC ( #972552=note: print w/replies, xml ) Need Help??

in reply to Coverage tool visibility within emacs

I am starting to put together some code for an emacs module that peers into Devel::Cover reports along the same lines as rcov-overlay.el, but also linking in linum-mode.el instead of highlighting the code lines themselves. I will need to port rcov-overlay.el, and also add a Devel::Cover formatting module to output the JSON used by the rcov-overlay module.

Sounds interesting but I didn't understand a word... Please, could you explain your goal in simple words avoiding to link to a lot of obscure lisp references?

  • Comment on Re: Coverage tool visibility within emacs

Replies are listed 'Best First'.
Re^2: Coverage tool visibility within emacs
by MidLifeXis (Monsignor) on May 29, 2012 at 12:37 UTC

    Emacs is a lisp interpreter disguised as an editor. The obscure lisp references are modules for that editor (think CPAN for Emacs). The rcov-overlay module calls ruby's coverage tool, brings the results back to emacs as a JSON data set, and highlights the resulting lines in the code that are covered or not. Linum is a module that shows line numbers in an emacs buffer, but allows you to customize what those line numbers look like.

    My goals are:

    • First, get the rcov-overlay port in place, but calling Devel::Cover tools instead. This would include returning the data in JSON format from Devel::Cover (currently does not exist). This would be (I think, I have only read the source) similar to Devel::Cover::Report::Vim. This would be in two parts - the rcov emacs component and the Perl module to generate the data.
    • Second, make use of the customization features of the linum module to be able to indicate (say with differently colored pipe symbols) what type of coverage is failed for a given line number.

    The first is to get the JSON reporting module in place, the second is to be able to get it identifying what is actually being reported. As an alternative for the second point, perhaps tooltips (hovertext, IntelliSense, whatever your editor's term of choice happens to be) might be the path to take. Not sure yet. Perhaps both will be selectable.

    Hope that clarifies it a bit.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://972552]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (3)
As of 2017-08-24 00:02 GMT
Find Nodes?
    Voting Booth?
    Who is your favorite scientist and why?

    Results (360 votes). Check out past polls.