> I've been using TextWrangler for a long time and have been seriously
> considering moving to BBEdit. However, I am a big fan of MacOS's new
> spelling correction functionality (Snow Leopard and newer), but don't see
> this kind of option in either product, although the latest documentation
> seems to lead me to think it does use the system spellcheck functionality.
At the bottom of the 'Text' menu in BBEdit. (not sure about TextWrangler)
> --Jaren
— dpk.
At the bottom of the 'Text' menu in BBEdit. (not sure about TextWrangler)

I don't consider it a bug that BBEdit does not try to spell for me. If it did, the first thing I would find out is how to turn it off. I do not often use the spell checker either. There are so many blocks of text that are not dictionary words that I use when I'm using BBEdit that an auto-correct would be more of a nuisance than a help.
If I need to write some text where I want that continual spelling feed-back, I use one of the many fine word processors that are available free or at cost. It is easy to write up text in a word processor, highlight and move it into BBEdit if need be.
My opinion is to thank Bare Bones for not including such a beast.
Respectfully,
Bucky
Primarily BBEdit is a text editor aimed as a tool for people writing
code so it follows to have a spell checker that tries to parse something
like:
`:dependencies [[org.clojure/clojure "1.3.0"]
[org.jclouds/jclouds "1.0" :classifier "jdk15"]
[net.sf.ehcache/ehcache "2.3.1" :type "pom"]
[log4j "1.2.15" :exclusions [javax.mail/mail
javax.jms/jms
com.sun.jdmk/jmxtools
com.sun.jmx/jmxri]]]`
or:
`var git = require( '../' );
git.repo( '../.git', function( err, repo ) {
if( err ) { throw new Error( err ); }
repo.commit( '59b20b8d5c6ff8d09518454d4dd8b7b30f095ab5', function(
err, commit ) {
if( err ) { throw new Error( err ); }
var history = commit.history();
history.on( 'commit', function() {
//console.log(arguments);
});`
as you're writing it & attempting auto-corrections would be unfeasible &
counter productive in my opinion.
I suspect that in the implementation of such a feature, the cons may
very well outweigh the pros for barebones but that, of course, is just
my opinion as a customer so take it with a very large pinch of salt :-)
Cheers,
Phil...
- --
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.
Wm. Shakespeare - Much Ado About Nothing
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPaX9CAAoJEKpMeDHWT5ADxJkH/2LprEO3CUzzEZdgDUm/13Ad
cg+bfY/6YLjVUezP39uPWptCCVzXoCs4IkglwAxIk6+sHBwdaVW86JnzitpSFnVU
Sd4C5CPjaIx/BH28WhAySef4to8CqxSs7s/+SpZVl1FlfbMTQYj8t/bKLfyD5VaJ
MN32srtQIj0PVd5GTACCHAzuNeQMn23W7wFOYJVpYWNbl8iR2KDJiS1IrXGnDlMj
tecEyHuD1Rm02UJGUtOz04pkRxbL0OLJSVeiatph7QapBslzJoDPtIbNYOHyS05h
5paa4kOsusO479ZU6vNACFr5mmu6UqyBI1f5Kkyr0XuzQZjl8WYbQVd0RGPUdWo=
=zvFt
-----END PGP SIGNATURE-----
> This is correct. BBEdit is slightly different, in that if I type slow
> enough, a little window will pop up and and suggest corrections, but
> this is not the native auto-correct functionality.
The window you refer to is "completions", which serve a different purpose.
> Would this be a viable issue (maybe even as a bug) to submit to BB?
It's on the giant list of things to do, but it's presently not near the top of the list.
Out of curiosity, what sort of writing are you using BBEdit for where this would be a useful addition?
Steve