commit all files in current working copy

[GoogleCodeExporter]

It would just be neat since commiting every file by itself really pushes
the version numbers.

Original issue reported on code.google.com by mappo.th...@gmail.com on 21 Sep 2008 at 10:09

[GoogleCodeExporter]

Original comment by bob.hies...@gmail.com on 24 Sep 2008 at 3:01

• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

+1

The ability to have a command (not just commit) operate on an entire source 
tree rather than a single file is 
very important.  I'd go so far as to say this is necessary before vcscommand 
becomes truly useful to me.

I'm willing to help contribute a patch for this, but I'd need some guidance on 
how best to do it.  I could 
imagine adding an addition option flag (ala allowNonZeroExit) to the dict for 
executing a command, but then I 
notice that commit uses a somewhat non-standard flow of execution in which that 
wouldn't really work. 

Bob, do you have something in mind for supporting commands that work on the 
tree (ie, don't specify a 
single file)?

Original comment by Threeve....@gmail.com on 21 Oct 2008 at 3:33

[GoogleCodeExporter]

It's still at the thought stage for me, because I don't find this function 
useful (at
the moment).  My initial approach would be to add a 'VCSCommitAll' command, but 
I
don't know whether that applies to the top of the tree, the current working
directory, or the directory of the current file.

The fact that each seems reasonable indicates to me that this is problematical.

Currently, you can edit a directory buffer (via netrw) and run VCSCommit, which 
works
recursively on that directory and all subdirectories.

Original comment by bob.hies...@gmail.com on 21 Oct 2008 at 7:17

[GoogleCodeExporter]

You can actually do this right now, since you can open the buffer for '.'
(esc-e-.-enter) then do a commit.

Original comment by adam.lu...@gmail.com on 31 Mar 2009 at 4:48

[GoogleCodeExporter]

I would really have to second this. I was kinda amazed this wasn't the default 
behavior 
and I just found out about it. I usually work on a lot of files at once to 
implement a 
feature etc, and don't want to have to commit every single file individually.

I'm using the Nerdtree plugin and the method proposed by #4 doesn't seem to 
work 
correctly.

Original comment by markmul...@gmail.com on 9 Sep 2009 at 8:48

[GoogleCodeExporter]

It works for me with netrw as it is described in #3 and #4, but what about 
multiple
files, but not ALL.

I can imagine 2 possible approaches:

1. Depending on argument, VCSCommit would:
 a) commit all modified files if argument is 'all' or '*', for instance;
 b) commit only files given as arguments;
 c) commit only current file if there is no argument.
2. Make 2 additional commands for: 1. all modified files and 2. multiple, but 
not all
modified files.

Original comment by mru...@gmail.com on 12 Jan 2010 at 10:59

[GoogleCodeExporter]

@markmulder
my workaround for the NERDTree issue is

let g:NERDTreeHijackNetrw = 0

Original comment by kom...@gmail.com on 13 Mar 2010 at 3:16

[GoogleCodeExporter]

I appear to be very unlikely to add this behavior.  I am always willing to 
review 
patches, though.

Original comment by bob.hies...@gmail.com on 29 Mar 2010 at 8:04

• Changed state: WontFix