Re: Proposal for a MacPorts'ish commit message template

On 2016-11-04 18:46, Lawrence Velázquez wrote: > Actually, I might have been thinking about another editor. My vim > highlights the subject in *green* up until 50 chars, and then black for > the overflow. But one can probably change that black to red if they want > :P .vimrc: hi def link

Re: Proposal for a MacPorts'ish commit message template

> On Nov 4, 2016, at 1:43 PM, Marko Käning wrote: > >> On 04 Nov 2016, at 18:34 , Lawrence Velázquez wrote: >> >> It doesn't really do anything differently w.r.t. wrapping, but it >> highlights subject-line overflow in an alarming red color. > >

Re: Proposal for a MacPorts'ish commit message template

Hi Larry, On 04 Nov 2016, at 18:34 , Lawrence Velázquez wrote: > It doesn't really do anything differently w.r.t. wrapping, but it > highlights subject-line overflow in an alarming red color. that’s a nice feature. Will have to test whether that works as documented in our

Re: Proposal for a MacPorts'ish commit message template

On 02 Nov 2016, at 23:33 , Ryan Schmidt wrote: > ...my initial reaction to your template (and my initial reaction when I saw > it mentioned previously) was "TL;DR”. I got it now. :) >> vim does that with syntax highlighting automatically nowadays when it >> notices

Re: Proposal for a MacPorts'ish commit message template

On 02 Nov 2016, at 01:03 , Lawrence Velázquez wrote: > To be honest, this template adds so much comment noise that I can't > imagine ever using it. That’s fine ok, your decision. :) >> --- ~/.git-commit-template --- >> # Please enter the commit message for your changes.

Re: Proposal for a MacPorts'ish commit message template

> On Nov 4, 2016, at 1:30 PM, Marko Käning wrote: > > Oh, I’d be using vim as well, good to know that it does support git. > I didn’t know that vim would be able to treat commit message line > formatting for the first and the 3r+ lines differently with 50 and 72 > chars

Re: Proposal for a MacPorts'ish commit message template

Hi, On 02 Nov 2016, at 00:08 , Clemens Lang wrote: > Developers are free to use your template if they want to. We don't want > to mandate using it though (since we couldn't enforce it anyway). yeah, I am aware of that. > vim does that with syntax highlighting automatically

Re: Proposal for a MacPorts'ish commit message template

On 2016-11-02 23:46, Ryan Schmidt wrote: >> Which editor are you using? It differs by editor. > > Well, you mentioned vim. Very occasionally I use that. I don't > remember seeing any particular syntax highlighting in it when editing > a commit message. You would need these settings in your

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:46:16PM -0500, Ryan Schmidt wrote: > Well, you mentioned vim. Very occasionally I use that. I don't > remember seeing any particular syntax highlighting in it when editing > a commit message. You need syntax highlighting (:syntax on) and ideally color enabled.

Re: Proposal for a MacPorts'ish commit message template

> On Nov 2, 2016, at 5:43 PM, Clemens Lang wrote: > > On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: >>> vim does that with syntax highlighting automatically nowadays when >>> it notices you are writing a commit message. If you need an >>> indication on your

Re: Proposal for a MacPorts'ish commit message template

On Wed, Nov 02, 2016 at 05:33:28PM -0500, Ryan Schmidt wrote: > > vim does that with syntax highlighting automatically nowadays when > > it notices you are writing a commit message. If you need an > > indication on your line width, may I suggest you configure your > > editor appropriately? > >

Re: Proposal for a MacPorts'ish commit message template

MacPorts used CVS commit templates 10 years ago. This was before my involvement with MacPorts, so I don't know how it was decided to do that in the first place or what developer opinions about it were. But you don't have to look at too much of the history of the repositories from 2006 and prior

Re: Proposal for a MacPorts'ish commit message template

> On Nov 1, 2016, at 6:51 PM, Marko Käning wrote: > > I know that many of you weren't in favour of a commit message template, > but I propose one anyway, which I derived from KDE’s neat one, as I find > it on the console quite handy to know when 50 or 72 characters are >

Re: Proposal for a MacPorts'ish commit message template

Hi, On Tue, Nov 01, 2016 at 11:51:52PM +0100, Marko Käning wrote: > I know that many of you weren't in favour of a commit message > template, but I propose one anyway, which I derived from KDE’s neat > one, Developers are free to use your template if they want to. We don't want to mandate using

Re: Proposal for a MacPorts'ish commit message template

On 01 Nov 2016, at 23:56 , Sterling Smith wrote: > Remind me, would using this template still give the commented git status > (which is the default)? Yes, make a change and test it like this: $ git commit -a -t ~/.git-commit-template The status gets appended at the

Re: Proposal for a MacPorts'ish commit message template

To answer myself, according to https://git-scm.com/book/tr/v2/Customizing-Git-Git-Configuration the answer is yes, there is still the commented git status. -Sterling On Nov 1, 2016, at 3:56PM, Sterling Smith wrote: > Remind me, would using this template still give the

Re: Proposal for a MacPorts'ish commit message template

Remind me, would using this template still give the commented git status (which is the default)? -Sterling On Nov 1, 2016, at 3:51PM, Marko Käning wrote: > Hi MacPorts’ GitHubians, > > I know that many of you weren't in favour of a commit message template, > but I

Proposal for a MacPorts'ish commit message template

Hi MacPorts’ GitHubians, I know that many of you weren't in favour of a commit message template, but I propose one anyway, which I derived from KDE’s neat one, as I find it on the console quite handy to know when 50 or 72 characters are reached in a line: --- ~/.git-commit-template --- #