Since it seems entirely possible that the subversion bundle developers do not read the intricate details of some LaTeX discussions I thought I would just highlight a couple of ideas that came out of yesterday's emails.
Could you make it more difficult to commit without a comment? For example if the comment is blank could you pop up a confirmation dialog? Or could you disable the commit button until something has been entered in the comment field?
Another suggestion was to have it so that the comment field gets the focus when the window pops up. Although this seems to be how it works for me already, so maybe this is done already.
Thanks,
Brad
Amen to that! :D
2007/8/15, Brad Miller bmiller@luther.edu:
Since it seems entirely possible that the subversion bundle developers do not read the intricate details of some LaTeX discussions I thought I would just highlight a couple of ideas that came out of yesterday's emails.
Could you make it more difficult to commit without a comment? For example if the comment is blank could you pop up a confirmation dialog? Or could you disable the commit button until something has been entered in the comment field?
Another suggestion was to have it so that the comment field gets the focus when the window pops up. Although this seems to be how it works for me already, so maybe this is done already.
Thanks,
Brad
-- Brad Miller Assistant Professor, Computer Science Luther College
On Aug 15, 2007, at 8:42 AM, Brad Miller wrote:
Could you make it more difficult to commit without a comment? For example if the comment is blank could you pop up a confirmation dialog? Or could you disable the commit button until something has been entered in the comment field?
And, while we're on the subject, I've been meaning to borrow some code from the TODO bundle so it can seed that comment field the CHANGED: comments from the target files (optionally removing those lines seems nice but potentially dangerous). It seems like this might be a useful generic feature for all of the version control bundles to use - does anything not use CommitWindow?
Chris
On Aug 17, 2007, at 7:43 PM, Chris Adams wrote:
On Aug 15, 2007, at 8:42 AM, Brad Miller wrote:
Could you make it more difficult to commit without a comment? For example if the comment is blank could you pop up a confirmation dialog? Or could you disable the commit button until something has been entered in the comment field?
And, while we're on the subject, I've been meaning to borrow some code from the TODO bundle so it can seed that comment field the CHANGED: comments from the target files (optionally removing those lines seems nice but potentially dangerous). It seems like this might be a useful generic feature for all of the version control bundles to use - does anything not use CommitWindow?
Chris
That sounds lovely, but I will never use that feature, and don't want it bogging down my commits if avoidable.
thomas Aylott — subtleGradient — CrazyEgg — bundleForge
On Aug 17, 2007, at 7:43 PM, Chris Adams wrote:
And, while we're on the subject, I've been meaning to borrow some code from the TODO bundle so it can seed that comment field the CHANGED: comments from the target files (optionally removing those lines seems nice but potentially dangerous). It seems like this might be a useful generic feature for all of the version control bundles to use
So basically you put the commit message in the source, and then when you commit, you “move” it to the commit window?
On Aug 24, 2007, at 9:26 AM, Allan Odgaard wrote:
So basically you put the commit message in the source, and then when you commit, you “move” it to the commit window?
Yes - I find the TODO bundle style more convenient than maintaining a separate changelog file, particularly since it's often easier just to add an inline comment while you're working (particularly when you've just taken care of a TODO/FIXME) and then later expand it for a formal changelog. This way // CHANGED: ... shows up in the commit window without the need to run diffs on everything and then I can expand that if needed.
Chris