From: Jakub Narebski <jnareb@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Adam Flott <adam@npjh.com>,
git@vger.kernel.org, Christian Stimming <stimming@tuhh.de>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] git-gui: Automatically spell check commit messages as the user types
Date: Mon, 04 Feb 2008 02:14:08 -0800 (PST) [thread overview]
Message-ID: <m3d4rd58ri.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080204084153.GA9997@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
> [This is also in my `pu` branch on repo.or.cz/git-gui.]
>
> As you can see the commit message was rather long. I used this
> feature the entire time while writing it, and I have to say, it
> saved me from my horrible spelling and typing skills. It also
> didn't feel like there was any significant lag, although every
> once in a while it will mark a word that you are in the middle
> of typing as misspelled, and catch up and correct that once you
> finish the word. I guess that's what you get for slowing down
> and taking a few extra milliseconds to move the fingers. :)
> Personally I prefer this style of spellchecking over the "lets show
> a modal dialog and ask the user to check one word at a time through
> the document". Mainly because this style gives you full context,
> while the modal dialog forms almost never do.
IMHO both modes have their use. The "flyspell" mode can show you
errors as you type, so you wouldn't repeat mistakes (running spelling
only on finished words is a good idea), the "modal dialog" has its use
for final chackup, as it is much easier in this mode to use "ignore"
or "ignore all" for the word which is not in dictionary and you know
it is correct, select one of proposed corrections or write your and
use "replace" or "replace all", and add word to local dictionary, and
change language (if done right of course, i.e. with highlighting and
going to the word currently being corrected, and not hiding/covering
the text being corrected so you can see the context).
BTW. you can check how Emacs does that in its flyspell-mode, and how
it does checking lazily; I guess the code should be readable even
knowing next to nothing about Emacs Lisp
> I'm not sure how to configure Aspell for other languages, it just
> magically came up with English on my system. Since git-gui has i18n
> support almost everywhere else I want to get that settled before
> this topic merges into my master branch. I've CC'd Christian and
> Johannes as they have been a big help in the past with the git-gui
> i18n effort and I would value any input they might have.
aspell {-d|--master}=<dictionary>
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-02-04 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 8:41 [PATCH] git-gui: Automatically spell check commit messages as the user types Shawn O. Pearce
2008-02-04 8:53 ` Wincent Colaiuta
2008-02-04 9:03 ` Shawn O. Pearce
2008-02-04 10:14 ` Jakub Narebski [this message]
2008-02-05 5:06 ` Adam Flott
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=m3d4rd58ri.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adam@npjh.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=stimming@tuhh.de \
/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).