deathaxe

The idea behind loading the tree object into a hidden view was to avoid loading it repetitively and save some time. As output panels are defined per window, GitGutter would...

> Now, not specifying by lines would be most problematic for Pygments Specifying lines fits most needs I think and is just enough. > How GitGutter chooses to use syntax_highlight_from_view...

> I am thinking about providing the ability to use a view, Sorry for my imprecise description of **a** view. 😄 Of course I had exactly this in mind. Referring...

mdpopups provides code highlighting out of the box. Therefore source which is known by mdpopups is highlighted in the diff popup as well as it is automatically put into a...

I'll definitely try to and find it doable, too.

Basically I can see three options: 1. Use the existing `protected_regions` 2. Add a new `popup_protected_regions` to disable diff popup for regions known to provide higher priority popup functionality. 3....

> I may not have access to the gitgutter popup and a quick "reset" You always have: ctrl+shift+alt+z > One gutter isn't enough... The "line changed" gutter is something special...

Hmm. Reading @FichteFoll's suggestion triggered the following idea: How about a dependency, which itself implements an EventListener that handles the on_hover(). It would than call an `on_request_popup()` method of all...

Sounds good. What if a package implements several event listeners which are meant to show popups? Call all `on_show_popup()` methods of that plugin and let it decide? How about the...

I like this idea as it should by quite easy to realize and seems straight forward. I was thinking about the approach suggested by PR #136 to combine diffs from...