From: Jimmy Tang <jtang+2007-01@tchpc.tcd.ie>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: commit message columns
Date: Mon, 22 Jan 2007 21:23:04 +0000 [thread overview]
Message-ID: <20070122212304.GA17243@vual.tchpc.tcd.ie> (raw)
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
next prev parent reply other threads:[~2007-01-22 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 21:19 commit message columns J. Bruce Fields
2007-01-22 21:23 ` Jimmy Tang [this message]
2007-01-22 21:44 ` J. Bruce Fields
2007-01-22 21:23 ` Shawn O. Pearce
2007-01-22 22:19 ` Matthias Lederhofer
2007-01-23 5:17 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070122212304.GA17243@vual.tchpc.tcd.ie \
--to=jtang+2007-01@tchpc.tcd.ie \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).