Re:A multi-purpose EDITOR variable
by asveikau on Saturday March 30, 2013 @07:55PM
(#5467099)
Don't a lot of programs first check for program-specific EDITOR values? So if you want to change the one for git, set GIT_EDITOR? Seems a lot cleaner than trying to recognize the filename.
Re:A multi-purpose EDITOR variable
by jlgreco on Sunday March 31, 2013 @01:14AM
(#5467795)
Frankly I don't see the point with Vim either, or any other editor that is capable of some concept of modes. Why doesn't the author find sublime suitable for git commit messages?
Re:A multi-purpose EDITOR variable
by alecdbrooks on Sunday March 31, 2013 @05:29AM
(#5468195)
I would guess it has something to do with Vim having a console version and Sublime not. Commit messages are so short he probably just wants it to pop up in his shell, rather than in another window.
Re:A multi-purpose EDITOR variable
by pilgrim689 on Saturday March 30, 2013 @08:34PM
(#5467189)
depends. for small commits, a one-liner suffices. For large commits, merge commits, etc., or for repos that require you to sign-off on the commit or whatnot, a one-liner followed by a blank line and then a nice paragraph or bullet-point list is necessary. "launching a full editor" is hardly a problem with emacsclient or vi[m]
Re:A multi-purpose EDITOR variable
by jordibunster on Sunday March 31, 2013 @04:59AM
(#5468146)
The smaller the commit, the more likely that it needs a proper explanation of why it was made.
When you find a commit from two years ago that changes a constant from -1 to -2, and the commit message says "constant change", or "bugfix in floobers" you're left with no context.
Re:A multi-purpose EDITOR variable
by ams6110 on Saturday March 30, 2013 @11:21PM
(#5467566)
$ commit -m 'This is
> my long
> multi-line message'
Granted, if you really want to write a novel that gets inconvenient, but I try to keep commit message short and reference a story or bug id# for more details when necessary.
Re:A multi-purpose EDITOR variable
by mhd on Saturday March 30, 2013 @10:55PM
(#5467505)
If I'm not using some integrated VCS system (which currently happens quite often), it's still mostly the case that I just switched from an editor when I'm writing my CLI commit command. So the mental context switch to transfer back into an editor setting is pretty minimal. And with the editor running (or EDITOR being vi(m)/emacsclient), the startup is negligible, too. So since the time of CVS, and now with either SVN or git, I just don't care too make a difference between small or larger commit messages and completely ignore options of expressing my commit message on the shell, going to the editor all the time.
I found that this also encourages me to be a bit more specific about the reasons for the changes committed. A few lines don't really hurt.
On the other hand, it might be that my commit schedule might still be too influenced by the older VCS systems, and a more frequent git-ish approach would encourage a more in-line approach. But right now I think that my one or two additional lines help more than they hurt.
Re:A multi-purpose EDITOR variable
by drivebyacct2 on Sunday March 31, 2013 @01:26AM
(#5467822)
Does Chrome use a different rendering in Linux? It looks fine here and I don't really have issues with fonts. (Except Calibri, people need to stop using it. It looks bad as is, and it looks awful in Linux without a bunch of manual hacks)
Re:A multi-purpose EDITOR variable
by Evbn on Sunday March 31, 2013 @02:23AM
(#5467907)
Not sure about windows, but Chrome definitely renders differently between Mac and Linux-- which is why Google Drive Presentations are not cross-platform -- spacing between objects gets messed up when you switch.
This is using a dispatch script as $EDITOR.
When you find a commit from two years ago that changes a constant from -1 to -2, and the commit message says "constant change", or "bugfix in floobers" you're left with no context.
I found that this also encourages me to be a bit more specific about the reasons for the changes committed. A few lines don't really hurt.
On the other hand, it might be that my commit schedule might still be too influenced by the older VCS systems, and a more frequent git-ish approach would encourage a more in-line approach. But right now I think that my one or two additional lines help more than they hurt.
Build up your commit with git add -p (which requires an editor), then git commit -v and check what you are committing again.
Regardless of that... I love this!