{"thread":{"id":"6481","subject":"commit message columns","startedAt":"2007-01-22T21:19:02Z","lastAt":"2007-01-23T05:17:20Z","messageCount":6,"participants":["J. Bruce Fields","Shawn O. Pearce","Jimmy Tang","Matthias Lederhofer","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"32339","messageId":"20070122211902.GC6614@fieldses.org","threadId":"6481","inReplyTo":null,"subject":"commit message columns","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-01-22T21:19:02Z","receivedAt":"2007-01-22T21:19:02Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"Uh, I feel like I must be missing something simple here--when editing\ncommit messages, you'd like the editor (vim in my case) to wrap text\nsooner than it normally would, since commit messages are displayed\nindented. What's the easiest way to ensure this always happens?\n\n--b.\n"},{"id":"32342","messageId":"20070122212304.GA17243@vual.tchpc.tcd.ie","threadId":"6481","inReplyTo":"20070122211902.GC6614@fieldses.org","subject":"Re: commit message columns","fromName":"Jimmy Tang","fromEmail":"jtang+2007-01@tchpc.tcd.ie","sentAt":"2007-01-22T21:23:04Z","receivedAt":"2007-01-22T21:23:04Z","isPatch":false,"sender":{"key":"jtang+2007-01@tchpc.tcd.ie","avatar":null},"body":"Hi,\n\nOn Mon, Jan 22, 2007 at 04:19:02PM -0500, J. Bruce Fields wrote:\n> Uh, I feel like I must be missing something simple here--when editing\n> commit messages, you'd like the editor (vim in my case) to wrap text\n> sooner than it normally would, since commit messages are displayed\n> indented. What's the easiest way to ensure this always happens?\n\nvim -c 'set tw=60'\n\nwhere 60 is the column width. dont know how useful that is to you though\n\n\nJimmy.\n\n\n-- \nJimmy Tang\nTrinity Centre for High Performance Computing,\nLloyd Building, Trinity College Dublin, Dublin 2, Ireland.\nhttp://www.tchpc.tcd.ie/ | http://www.tchpc.tcd.ie/~jtang\n"},{"id":"32340","messageId":"20070122212359.GC29975@spearce.org","threadId":"6481","inReplyTo":"20070122211902.GC6614@fieldses.org","subject":"Re: commit message columns","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-01-22T21:23:59Z","receivedAt":"2007-01-22T21:23:59Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"\"J. Bruce Fields\" wrote:\n> Uh, I feel like I must be missing something simple here--when editing\n> commit messages, you'd like the editor (vim in my case) to wrap text\n> sooner than it normally would, since commit messages are displayed\n> indented. What's the easiest way to ensure this always happens?\n\n\nUse git-gui. The message buffer window doesn't linewrap nor does\nit scroll, so you learn to linewrap on your own. :-)\n\n\nWhen I'm not in git-gui I use vile and have a macro in it to\npass the current paragraph of text through:\n\n fmt --crown-margin --width=70 --uniform-spacing\n\nworks reasonably well.\n\n-- \nShawn.\n"},{"id":"32341","messageId":"20070122214419.GD6614@fieldses.org","threadId":"6481","inReplyTo":"20070122212304.GA17243@vual.tchpc.tcd.ie","subject":"Re: commit message columns","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-01-22T21:44:19Z","receivedAt":"2007-01-22T21:44:19Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Mon, Jan 22, 2007 at 09:23:04PM +0000, Jimmy Tang wrote:\n> Hi,\n> \n> On Mon, Jan 22, 2007 at 04:19:02PM -0500, J. Bruce Fields wrote:\n> > Uh, I feel like I must be missing something simple here--when editing\n> > commit messages, you'd like the editor (vim in my case) to wrap text\n> > sooner than it normally would, since commit messages are displayed\n> > indented. What's the easiest way to ensure this always happens?\n> \n> vim -c 'set tw=60'\n> \n> where 60 is the column width. dont know how useful that is to you though\n\nI was trying to figure out how to get that for git's invocations of vim,\nbut not all others.\n\nBut, come to think of it, maybe I'd rather have the textwidth just be 72\neverywhere.\n\n--b.\n"},{"id":"32344","messageId":"20070122221927.GA3746@moooo.ath.cx","threadId":"6481","inReplyTo":"20070122211902.GC6614@fieldses.org","subject":"Re: commit message columns","fromName":"Matthias Lederhofer","fromEmail":"matled@gmx.net","sentAt":"2007-01-22T22:19:27Z","receivedAt":"2007-01-22T22:19:27Z","isPatch":false,"sender":{"key":"matled@gmx.net","avatar":null},"body":"J. Bruce Fields wrote:\n> Uh, I feel like I must be missing something simple here--when editing\n> commit messages, you'd like the editor (vim in my case) to wrap text\n> sooner than it normally would, since commit messages are displayed\n> indented. What's the easiest way to ensure this always happens?\n\nYou could add this to your .vimrc:\n> autocmd BufNewFile,BufRead .git/COMMIT_EDITMSG setlocal tw=60 ft=human\nHas anyone a good filetype for this?\n"},{"id":"32364","messageId":"20070123051720.GA24259@coredump.intra.peff.net","threadId":"6481","inReplyTo":"20070122221927.GA3746@moooo.ath.cx","subject":"Re: commit message columns","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2007-01-23T05:17:20Z","receivedAt":"2007-01-23T05:17:20Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jan 22, 2007 at 11:19:27PM +0100, Matthias Lederhofer wrote:\n\n> You could add this to your .vimrc:\n> > autocmd BufNewFile,BufRead .git/COMMIT_EDITMSG setlocal tw=60 ft=human\n> Has anyone a good filetype for this?\n\nI do the same thing, but I use filetype=gitcommit. Then it picks up the\nsyntax highlighting file automatically (see contrib/vim).\n\n-Peff\n"}]}