From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Haines Brown Newsgroups: gmane.emacs.help Subject: Re: Automatic flyspell Date: Sun, 22 Feb 2015 04:46:52 -0500 Message-ID: <87ioeuwa5v.fsf@engels.histomat.net> References: <87twyg5y5e.fsf@engels.histomat.net> <87zj86n53i.fsf@debian.uxu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1424598628 19175 80.91.229.3 (22 Feb 2015 09:50:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Feb 2015 09:50:28 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Feb 22 10:50:23 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YPTB4-0004q7-Ft for geh-help-gnu-emacs@m.gmane.org; Sun, 22 Feb 2015 10:50:18 +0100 Original-Received: from localhost ([::1]:39552 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YPTB3-0000Oo-GH for geh-help-gnu-emacs@m.gmane.org; Sun, 22 Feb 2015 04:50:17 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!Xl.tags.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail Original-NNTP-Posting-Date: Sun, 22 Feb 2015 03:46:52 -0600 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:YqCKMyB8G/vulMIBHwOQ09EFUkQ= Original-Lines: 56 X-Usenet-Provider: http://www.giganews.com Original-X-Trace: sv3-wncdIT0P9jfcy97WTJV7fFF7NrrHaecmQyWWmziP2IOrxiqdSBcTctZVFbu6FjCMR5kW66Pph0LBd+0!TdlBoNe91O+7PnZge+cniWnsJI+IaaTWjvlqytLH/bsyiNnHn145GpvTShD5AQ== Original-X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3275 Original-Xref: usenet.stanford.edu gnu.emacs.help:210553 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:102830 Archived-At: Emanuel Berg writes: > Haines Brown writes: > >> In exploring how to get flyspell enabled for all >> text files, I get impression these should work, but >> despite them I remain in the Fundamental mode with >> the only minor mode being Fill. > > Aha, now I think I understand. Do you want to use > text-mode for files like README but you end up in > fundamental-mode? > > If so, try this: > > (set-default 'major-mode 'text-mode) Emanuel, thanks. I actually have Flyspell working in Fundamental mode with these lines: (defun turn-on-flyspell () (flyspell-mode 1)) (add-hook 'find-file-hooks 'turn-on-flyspell) For example it is on now as I write, and my present modes are Message Fly MML Abbrev Fill Narrow. This probably because I started gnus in emacs with the two lines above in its init file. When I start emacs its modes are Lisp Interaction Fill. When I then open a text file with it, the modes change to Fundamental Fly Fill. So it seems that flyspell is working in Fundamental mode. If I give a test text file an .txt extension, emacs opens in the Text Fly Fill modes. I see no difference off hand from when I open that file without the extension in the Fundamental Fly Fill modes or with it in the Text mode. This raises a question, why should I set default to Text mode? All my work is done in LaTeX mode rather than use a word processor (I used to use WordPerfect under DOS, but have little idea how to use these GUI things---too complicated for my antiquated brain). However, for LaTeX emacs uses a different init file with the lines: (defun turn-on-flyspell () (flyspell-mode 1)) (add-hook 'find-file-hooks 'turn-on-flyspell) When the emacs session I initially mentioned opens a .tex file, it opens in the LaTeX Fly Fill modes and knows not to mark commands or environments such as \subsection{} as misspellings. When I open a .java file I'm in the Java/1 Fly Abbrev Fill modes. When I open a .c file, I'm in the C/1 Fly Abbrev Fill modes. In these cases commands are marked as misspellings. If I did any serious programming I'd have to tailor Flyspell for those modes. Haines