From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lute Kamstra Newsgroups: gmane.emacs.devel Subject: Re: enriched-mode problems Date: Thu, 16 Jun 2005 13:45:14 +0200 Message-ID: <87mzpqbk51.fsf@xs4all.nl> References: <20050615.070838.116346726.wl@gnu.org> <87u0jzsr9i.fsf@xs4all.nl> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1118922272 23798 80.91.229.2 (16 Jun 2005 11:44:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Jun 2005 11:44:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 16 13:44:29 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DisnB-00005t-9E for ged-emacs-devel@m.gmane.org; Thu, 16 Jun 2005 13:44:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dissa-0005Mw-8D for ged-emacs-devel@m.gmane.org; Thu, 16 Jun 2005 07:49:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DisrS-0004y0-Mq for emacs-devel@gnu.org; Thu, 16 Jun 2005 07:48:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DisrO-0004vz-TP for emacs-devel@gnu.org; Thu, 16 Jun 2005 07:48:40 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DisrN-0004ti-LT for emacs-devel@gnu.org; Thu, 16 Jun 2005 07:48:37 -0400 Original-Received: from [194.109.24.35] (helo=smtp-vbr15.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dispq-00080G-E3; Thu, 16 Jun 2005 07:47:02 -0400 Original-Received: from pijl (a80-127-67-124.adsl.xs4all.nl [80.127.67.124]) by smtp-vbr15.xs4all.nl (8.13.3/8.13.3) with ESMTP id j5GBjF9o086141; Thu, 16 Jun 2005 13:45:15 +0200 (CEST) (envelope-from Lute.Kamstra@xs4all.nl) Original-Received: from lute by pijl with local (Exim 3.36 #1 (Debian)) id 1Diso6-0003qG-00; Thu, 16 Jun 2005 13:45:14 +0200 Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Thu, 16 Jun 2005 00:07:57 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) Original-Lines: 35 X-Virus-Scanned: by XS4ALL Virus Scanner X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:38950 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:38950 Richard Stallman writes: > I've got the same problem with auto-fill sometimes. I switch that > mode on with text-mode-hook. When I visit a text file that has "mode: > auto-fill", it is effectively turned off. Maybe we should do > (some-minor-mode 1) for "mode: some-minor-mode" constructs. > > That would be hard, since the code doesn't know whether the mode > is a minor or major mode. Can't you tell a major mode from a minor mode by looking at the argument list? > But worse than that, it is misguided. > > It would be a mistake to try to make this "work", since it is > misguided ayway. Minor modes such as auto-fill mode are personal > choices; files should not specify them at all. While I tend to agree with you in theory (for the case of auto-fill mode), the problem still bites me in practice. I don't control all files I visit. Other people might put "mode: auto-fill" in a file and that will cause problems for me. Also, it is quite clear that someone intends to turn auto-fill on in that case. So why not do that instead of toggling? > It might be useful to find a way to arrange a warning when files use > Mode: or -*-...-*- to specify minor modes. In general, there are examples of minor modes (Ralf and David gave an example) for which it is useful to turn them on (or off) for a certain file because of the _contents_ of that file. So it would be nice to have a mechanism to do this. Lute.