[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] [Subclipse-dev] Edit while commit

From: Andreas Haferburg <haferbur_at_inf.fu-berlin.de>
Date: Wed, 15 Dec 2010 15:48:28 +0100

On 12/15/2010 11:08 AM, Mikhail Barg wrote:
> On 14.12.2010 20:57, Stephen Elsemore wrote:
>> Since it is easy to use the Synchronize view to see which resources are
>> ready to be committed, and to perform editable compares on those resources
>> if necessary prior to committing, my feeling is that it's not worth changing
>> the commit dialog.

The unique feature of the Commit dialog is the editor for the commit
message. Obviously I'd like to use this editor to compose the commit
message. While composing the commit message I basically explain my
changes to someone else, and while doing that I often notice that I
should put similar explanations in the code as well.

Here's how I normally work:
- synchronize
- select files to commit
- open commit dialog
- go through all the changes while adding items to the commit message
- click ok

I can't do that in Synchronize view because I can't compose the commit
message there. But if I want to edit something I have to close the
Commit dialog, and afterwards select the files to commit again, reopen
the dialog, then continue composing the commit message. I usually open
the file from the Synch View, which also means that I lose the selection
of the files to commit.

The best way I found so far: Paste the names of the files to commit into
VIM, compose the commit message there using the Synch view, then go
through the list of files again to select them in Subclipse, open the
commit editor, paste the message, commit. In other words it's best not
to use the Commit dialog for composing the commit message.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-12-15 15:48:48 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.