Super Git Senses (Gedit Plugin)
We don't really need buttons that commit changes or any of that nonsense, we have a console for that. What we really need is to have intelligent feedback from Gedit about what's going on with Git, something that's always there for us to see but can be comfortably ignored too. We can use the console to DO Git things, but why not be AWARE of more things while coding? Let's improve our workflow by getting Super Git Senses.
Sponsor This Project
Bounty:
US $16.58(Sponsor Project) Sponsor This Project
You currently need to log in to sponsor a project. We apologize for the inconvenience.
Note: You can propose changes using the forum below.
We don't really need buttons that commit changes or any of that nonsense, we have a console for that. What we really need is to have intelligent feedback from Gedit about what's going on with Git, something that's always there for us to see but can be comfortably ignored too. We can use the console to DO Git things, but why not be AWARE of more things while coding? Let's improve our workflow by getting Super Git Senses.
Goals:
1. Mark changed lines since the last commit so we can instantly find the code we're working on, just like this: http://1dan.org/gedit-plugins/highlight-edited-lines/ except aware of Git commits. 2. Mark changed files in the file explorer tab too, if possible.
Considerations:
- Remember that undoing or reverting a line back to its original state must unmark the line, unlike the highlight-edited-lines plugin.
- What should happen when we commit in our console then come back to Gedit?
- Perhaps we should also mark changes since the last but one commit (with another colour)?
Does anyone have any further suggestions? Would you like to see this plugin come to life? Why not add a few dollars to the bounty? Or just code the plugin and claim the bounty :)
Goals:
1. Mark changed lines since the last commit so we can instantly find the code we're working on, just like this: http://1dan.org/gedit-plugins/highlight-edited-lines/ except aware of Git commits. 2. Mark changed files in the file explorer tab too, if possible.
Considerations:
- Remember that undoing or reverting a line back to its original state must unmark the line, unlike the highlight-edited-lines plugin.
- What should happen when we commit in our console then come back to Gedit?
- Perhaps we should also mark changes since the last but one commit (with another colour)?
Does anyone have any further suggestions? Would you like to see this plugin come to life? Why not add a few dollars to the bounty? Or just code the plugin and claim the bounty :)
Change History:
- 2011-06-24 17:45 EDT [ACCEPTED] No subject
