From: Hongxu Chen <leftcopy.chx@gmail.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How can I made ispell more smarter for some code blocks?
Date: Wed, 15 May 2013 23:01:08 +0800 [thread overview]
Message-ID: <87li7g479n.fsf@gmail.com> (raw)
In-Reply-To: <87k3n02vxg.fsf@mithlond.arda> (Teemu Likonen's message of "Wed, 15 May 2013 16:51:23 +0300")
Thanks for your introduction. I took a glimpse at the project and found
that the inline docs and README is wonderful, so I also believe this is
a fabulous tool. But I feel that it might not meet my needs and seems
that configuration is a bit difficult due to its flexibility.
But I might have a try.
Many thanks!
Hongxu Chen
Teemu Likonen <tlikonen@iki.fi> writes:
> Hongxu Chen [2013-05-15 17:13:17 +08:00] wrote:
>
>> I use aspell for spell-check when I writing notes with markdown/org or
>> simple emails. What annoys me that it just checks too much. For
>> instance, it even checks the content inside code-blocks in org mode,
>> which is false positive terminologically. So is there way to make it
>> smarter?
>
> This is an advertisement.
>
> I wanted a smarter and faster spelling checker, so I ended up
> implementing wcheck-mode:
>
> https://github.com/tlikonen/wcheck-mode
>
> (Also through Marmalade.)
>
> But wcheck-mode doesn't work well with aspell because aspell buffers its
> output. Wcheck-mode works with anything that works line-wise through
> standard input and output. Sorry. You could use Enchant as a wrapper for
> other spelling checkers.
>
> Wcheck-mode checks only visible text area, that is, no text outside
> windows and no invisible text. You can also configure which "faces" it
> checks and which ones it skips.
--
Regards,
Hongxu Chen
prev parent reply other threads:[~2013-05-15 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 9:13 How can I made ispell more smarter for some code blocks? Hongxu Chen
2013-05-15 13:51 ` Teemu Likonen
2013-05-15 14:55 ` Rasmus
2013-05-15 15:03 ` Teemu Likonen
2013-05-15 15:01 ` Hongxu Chen [this message]
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=87li7g479n.fsf@gmail.com \
--to=leftcopy.chx@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tlikonen@iki.fi \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.