[petsc-dev] Barry, why would you do such a thing?
Satish Balay
balay at mcs.anl.gov
Thu Jan 5 11:40:50 CST 2012
On Thu, 5 Jan 2012, Barry Smith wrote:
>
> On Jan 5, 2012, at 11:28 AM, Jed Brown wrote:
>
> > On Thu, Jan 5, 2012 at 11:25, Barry Smith <bsmith at mcs.anl.gov> wrote:
> > You fix hg so it is not such a piece of shit that doesn't tell you what you changed by default, then this won't happen again. What the fuck do the mecurial developers think, I have any memory capacity at all?
> >
> > When running from the command line, I use hg diff before hg commit.
>
> That requires me to do an extra step before I know I have to do that extra step (it is only have that I have typed hg commit that I see a mystery file that I didn't know I changed.) So now it is a many step process
>
> hg commit ! crap see something in their I don't understand
> exit emacs without saving
> hg diff
> hg revert
> hg commt
>
> >
> > I take it you have tried TortoiseHG, SourceTree, etc, and they don't do what you want?
>
> The problem with the GUI's is that they are ALL GUI, so I have to hunt down the GUI icon, click on some buttons then close the GUI window manually. While with command line I am right there and hg commit, pull, push etc can be executed much faster
>
> What I want is the the editor that opens with commit display each file changed and below some of the diffs. And then in the editor I can mark any of the diffs if I chose as revert or as don't include in commit. Is that too much to ask?
You want 'record' functionality for 'commit'. Yeah - it doesn't take commands from
emacs - and has its own interactive command interface.
So you can add the following to ~/.hgrc to make it default for 'commit'
>>>>
[alias]
commit = record
<<<<<
> Or an hg commit that opens a simple GUI just for the commit (instead of an editor) with all possible options of revert etc (bk had this 10+ years ago and hg still doesn't have it).
>
'qct has this - but then its not easy to install on mac.
Satish
More information about the petsc-dev
mailing list