On Thu, 2020-03-26 at 08:26 -0500, Eric Blake wrote:
> On 3/25/20 9:09 PM, Hu, Robert wrote:
> > (Don't know why my Linux-Evolution missed this mail.)
> > > -----Original Message-----
> > > Long line; it's nice to wrap commit messages around column 70 or
> > > so (because
> > > reading 'git log' in an 80-column window adds indentation).
> > >
> >
> > [Hu, Robert]
> > I think I set my vim on wrap. This probably escaped by paste.
> > I ran checkpatch.pl on the patches before sending. It escaped check
> > but didn't
> > escaped your eagle eye😊 Thank you.
>
> checkpatch doesn't flag commit message long lines. Maybe it could
> be
> patched to do so, but it's not at the top of my list to write that
> patch.
>
> >
> > > > I just fix a boudary case on his original patch.
> > >
> > > boundary
> >
> > [Hu, Robert]
> > Emm... again spell error. Usually I would paste descriptions into
> > some editors
> > with spell check, but forgot this time.
> > Vim doesn't have spell check I think. What editor would you suggest
> > me to
> > integrate with git editing?
>
> I'm an emacs user, so I have no suggestions for vim, but I'd be very
> surprised if there were not some vim expert online that could figure
> out
> how to wire in a spell-checker to vim. Google quickly finds:
> https://www.ostechnix.com/use-spell-check-feature-vim-text-editor/
>
nice, thanks:)