git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: commit message columns

From
JTJimmy Tang <jtang+2007-01@tchpc.tcd.ie>
Date
Jan 22, 2007, 21:23 UTC
Message-ID
<20070122212304.GA17243@vual.tchpc.tcd.ie>
In-Reply-To
<20070122211902.GC6614@fieldses.org>
Hi,
On Mon, Jan 22, 2007 at 04:19:02PM -0500, J. Bruce Fields wrote:
> Uh, I feel like I must be missing something simple here--when editing
> commit messages, you'd like the editor (vim in my case) to wrap text
> sooner than it normally would, since commit messages are displayed
> indented.  What's the easiest way to ensure this always happens?
vim -c 'set tw=60'
where 60 is the column width. dont know how useful that is to you though
Jimmy.
-- 
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/ | http://www.tchpc.tcd.ie/~jtang
Previous: J. Bruce FieldsNext: J. Bruce Fields
Message 2 of 6 in “commit message columns”
  1. J. Bruce FieldsJan 22, 2007
  2. Jimmy TangJan 22, 2007
  3. J. Bruce FieldsJan 22, 2007
  4. Shawn O. PearceJan 22, 2007
  5. Matthias LederhoferJan 22, 2007
  6. Jeff KingJan 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.