On Jun 16, 2011, at 12:10 PM, Tim Gray wrote: >> On Jun 15, 2011 at 10:53 AM -0400, Eric Weir wrote: > > If *all* you ever type in is documents with prose, and they might have > different extensions depending on your mood, you might be better served with: > > set spell spelllang=en
Probably so. I was led to try to limit it to files with a "txt" extent by something I read about having spell on for every filetype could lead to overloading of memory. However, I never have more than a few small files open at one time, so maybe I should just forget about that and turn spell on for everything. >> I have a file for a plugin in ~/.vim/after/plugin. I wouldn't want to >> replace it. Could I simply add another? > > Assuming that the MultiMarkdown filetype is called 'multimarkdown', you would > create a vim file called ~/.vim/after/ftplugin/multimarkdown.vim. Inside > that file, you would write: > setlocal spell spelllang=en > > along with any other commands or settings you want for MultiMarkdown files. > > If you are only interested in turning on spelling for that file type and > nothing else, it might be simpler to just define the following in your .vimrc: > > au FileType multimarkdown setlocal spell spelllang=en Thanks. This is helpful, though for the time being, until there's a reason to do so, I think that I'll forego this approach for the simpler one of just turning spelling on for everything. > Sorry if this is all a lot to take in and I am too verbose. I think it would > probably help if you read up on vim filetypes and how they differ from file > extensions and names. Sometimes they represent the same thing, sometimes not. You're not too verbose. I appreciate your patience with me. At this stage, almost everything about Vim is "a lot to take in." I expect that. I also expect that in time, for my needs and uses, it will come together. It's happened before. And, yes, I definitely need to read up on filetypes. [I noticed this morning that there's an item under Syntax in the menu bar for "show filetypes in menu." I clicked it. Just that list made it clear that filetype is something very different from what I assumed, i.e., files associated with different languages and applications.] Thanks again, ------------------------------------------------------------------------------------------ Eric Weir Decatur, GA USA [email protected] -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
