From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Birger Skogeng Pedersen <birger.sp@gmail.com>
Cc: Pratyush Yadav <me@yadavpratyush.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] git-gui: warn if the commit message contains lines longer than the set limit
Date: Thu, 5 Sep 2019 19:46:29 +0200 [thread overview]
Message-ID: <CAKPyHN1VeK4bR3Dn5yjrs2UwT5XGKOPU_FHaMBsP+riM-bjeWA@mail.gmail.com> (raw)
In-Reply-To: <CAGr--=J1YmMbud4tcZjAZ06m0CmRbAqQTzs+FTgeJkJp4d2FzQ@mail.gmail.com>
On Thu, Sep 5, 2019 at 8:50 AM Birger Skogeng Pedersen
<birger.sp@gmail.com> wrote:
>
> On Thu, Sep 5, 2019 at 12:48 AM Pratyush Yadav <me@yadavpratyush.com> wrote:
> > I'll chime in with what I think would be a great solution: auto word
> > wrapping. This way, the users can set the text width, and not have to
> > worry about manually formatting it. Long "words" like URLs would still
> > get to be on one line, and we avoid showing annoying dialogs.
>
> +1. IMO git-gui really needs automatic word wrapping for the commit messages.
Please exclude the first line, i.e., the subject. This should not be
wrapped at all.
I also imagine, that we should make it configurable, I'm unsure if I
would use this feature for my self.
Bert
>
> Birger
next prev parent reply other threads:[~2019-09-05 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 20:10 [PATCH 1/2] git-gui: warn if the commit message contains lines longer than the set limit Bert Wesarg
2019-09-04 20:10 ` [PATCH 2/2] git-gui: add horizontal scrollbar to commit buffer Bert Wesarg
2019-09-04 20:31 ` Eric Sunshine
2019-09-04 20:46 ` Bert Wesarg
2019-09-10 20:28 ` Pratyush Yadav
2019-09-12 19:10 ` Bert Wesarg
2019-09-04 20:29 ` [PATCH 1/2] git-gui: warn if the commit message contains lines longer than the set limit Eric Sunshine
2019-09-04 20:43 ` Bert Wesarg
2019-09-04 22:48 ` Pratyush Yadav
2019-09-05 6:48 ` Birger Skogeng Pedersen
2019-09-05 17:46 ` Bert Wesarg [this message]
2019-09-06 14:08 ` Birger Skogeng Pedersen
2019-09-06 20:07 ` Philip Oakley
2019-09-10 8:04 ` David Aguilar
2019-09-10 19:42 ` Pratyush Yadav
2019-09-05 6:21 ` Johannes Sixt
2019-09-05 17:43 ` Bert Wesarg
2019-09-10 16:50 ` Johannes Sixt
2019-09-12 19:26 ` Bert Wesarg
2019-09-10 20:34 ` Pratyush Yadav
2019-09-12 19:13 ` Bert Wesarg
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKPyHN1VeK4bR3Dn5yjrs2UwT5XGKOPU_FHaMBsP+riM-bjeWA@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=birger.sp@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.com \
--cc=sunshine@sunshineco.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).