From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Automatic flyspell
Date: Wed, 25 Feb 2015 18:01:47 +0100 [thread overview]
Message-ID: <8761aqc4ck.fsf@debian.uxu> (raw)
In-Reply-To: mailman.708.1424725551.31049.help-gnu-emacs@gnu.org
Robert Thorpe <rt@robertthorpeconsulting.com> writes:
> Flyspell-prog-mode is supposed to check only
> comments and strings. I tried it in C mode just
> before writing my previous post and it seemed to
> only check the strings.
OK, I suspected that since there were two versions.
Yes, that's intelligent but perhaps a bit overkill. It
depends how many strings you have and how poor your
spelling is, I suppose. Unless it comes with a big
overhead it is nothing to worry about.
> In the post you quote though I was giving advice to
> someone who said they wanted flyspell everywhere.
Well, I just thought about it when I saw the
collective prog-mode-hook - you mean I should have
quoted it differently to make explicit the advice was
given to the OP and not you?
Yes, I think it is the right attitude to help people
even though you would have solved the problem in
another way (including degrading it from problem
status). That's what I try to do whenever I can but I
also don't have a problem adding a note what I think
on a larger scale. If I however only would give such
comments that would have been a bad attitude indeed.
--
underground experts united
next parent reply other threads:[~2015-02-25 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.708.1424725551.31049.help-gnu-emacs@gnu.org>
2015-02-25 17:01 ` Emanuel Berg [this message]
[not found] <mailman.664.1424663182.31049.help-gnu-emacs@gnu.org>
2015-02-23 19:19 ` Automatic flyspell Emanuel Berg
2015-02-23 21:05 ` Robert Thorpe
2015-02-20 16:46 Haines Brown
2015-02-21 23:38 ` Emanuel Berg
2015-02-22 0:48 ` Emanuel Berg
2015-02-22 9:46 ` Haines Brown
2015-02-22 23:24 ` Emanuel Berg
2015-02-23 3:46 ` Robert Thorpe
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=8761aqc4ck.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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.
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.