Request

[GoogleCodeExporter]

Is it possible to get log message generated from the commit program itself 
for commiting instead of:

VCS:----

something like:

M file.c
A file2.c

Original issue reported on code.google.com by domid...@gmail.com on 26 Mar 2008 at 11:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

As the commits introduced by vcscommand are typically single-file-oriented, this
request doesn't make sense.

In the case that you executed VCSCommit on a directory, you could just as easily
execute VCSStatus and pull the information into the commit log.

Finally, there is no interaction with the commit program until the commit 
message is
prepared, as there is no easy way to tell the VCS commit to interact with an 
existing
editing session.  It is probably possible to pull some tricks using vim remote
capabilities, but that seems like a lot of trouble for very little gain.

Thank you,

bob

Original comment by bob.hies...@gmail.com on 26 Mar 2008 at 12:38

[GoogleCodeExporter]

It does make sense for me. Because I want to check in without having to type
anything but I want to have the modified files in the log.
Why do I need a static message like:
VCS .....
when I can have the changed files, which is also the default behaviour of SVN.

Using VCSStatus is a good tip, thanks. It is not so easy to implement a general
solution with VCSStatus because the result is given back in a new buffer. I
managed to solve the problem for me for svn and cvs. I'm happy with this
solution and you can ignore my request if you think it is not needed.

Thanks a lot for the fast replay.
Regards,
Dimitar

Original comment by domid...@gmail.com on 27 Mar 2008 at 7:14

[GoogleCodeExporter]

I say it doesn't make sense because when you run VCSCommit, you are only 
committing
the current file, and no others.  That's why pre-populating the list with 
currently
modified files is the wrong thing to do, because those files (other than the 
current
one) will NOT be committed.

On an unrelated note, SVN can show changed files when you do a multi-file commit
because it is already in a commit context, if that makes sense.  When you are 
writing
a commit message in VIM for VCSCommit, the VCS (for instance SVN) does not know 
there
is about to be a commit, it is invoked directly with the completed commit log 
all at
once (that is, it is not interactive the way letting SVN invoke your $EDITOR 
is).

Thank you,

bob

Original comment by bob.hies...@gmail.com on 27 Mar 2008 at 1:16