Community
Participate
Working Groups
It should be possible to place a "${cursor}" variable into commit templates. This would be the location where the cursor should wait for user input when the commit dialog pops up. This functionality would be similar to the one provided in the Java editor. It should encourage users to enter a meaningful commit message. The default Mylyn template is not very useful from an SCM log point of view if multiple commits are made for the same task number and some changes are actually refactorings not really related to that task. -- Configuration Details -- Product: Eclipse SDK 3.6.0.v201001291300 (org.eclipse.sdk.ide) Installed Features: org.eclipse.mylyn_feature 3.4.0.I20100204-0200-e3x
That sounds like a great idea. Unfortunately this would require support from each team provider since the commit dialog is provider specific as far as I know. I have moved this bug to CVS. Please free to bounce back to Mylyn if there is already support for controlling the cursor position in the commit message dialog.
Stefen or Gunnar, are you considering providing a patch to fix that in the CVS provider? It should not be hard. I think you should raise similar bugs for other providers like Subversive or EGit.
My understanding was that the commit templates are a general feature provided by Mylyn. After all, that's the location in the preferences where I - as a user - would use that variable. I'm not sure how Mylyn injects the message into the various commit dialogs today. But it seems that the only requirement for CVS team provider is exposing some API to control the cursor positioning within the commit dialog. But, I don't have the time to contribute a complete patch story here.
(In reply to comment #1) > Please free to bounce back to Mylyn if there is > already support for controlling the cursor position in the commit message > dialog. (In reply to comment #3) > But it seems that the only requirement for CVS team provider is exposing > some API to control the cursor positioning within the commit dialog. There is no such API at the moment. I guess this will have to wait for a volunteer that would provide an initial patch.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
