From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: steinab@ifi.uio.no (Steinar =?iso-8859-1?Q?B=F8rmer?=) Newsgroups: gmane.emacs.help Subject: Re: Is Emacs becoming Word? Date: Sun, 27 Mar 2005 12:05:11 +0200 Organization: :noitazinagrO Message-ID: <867jjtmmjs.fsf@pallotta.studby.uio.no> References: <01c53229$Blat.v2.4$f7086e60@zahav.net.il> <01c53202$Blat.v2.4$fc3ff320@zahav.net.il> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1111923048 19260 80.91.229.2 (27 Mar 2005 11:30:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 27 Mar 2005 11:30:48 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Mar 27 13:30:47 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DFVyd-0004X1-86 for geh-help-gnu-emacs@m.gmane.org; Sun, 27 Mar 2005 13:30:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DFW8P-0003zF-9j for geh-help-gnu-emacs@m.gmane.org; Sun, 27 Mar 2005 06:40:49 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!canoe.uoregon.edu!newshub.sdsu.edu!npeer.de.kpn-eurorings.net!uio.no!quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 58 Original-NNTP-Posting-Host: ti400720a081-14465.bb.online.no Original-X-Trace: quimby.gnus.org 1111921364 20986 85.164.248.129 (27 Mar 2005 11:02:44 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: Sun, 27 Mar 2005 11:02:44 +0000 (UTC) User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (berkeley-unix) Cancel-Lock: sha1:8vB67UVBZE6x8SwK6GG2iBiPYSU= Original-Xref: shelby.stanford.edu gnu.emacs.help:129658 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:25211 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:25211 Greg Novak wrote: | * Eli Zaretskii wrote: | > This is off by default, so you should look into your customizations | > and find what turns it on. | > ... | > This feature is off by default as well. Something in your .emacs | > turns it on. | > ... | > So I think the response was appropriate, and precisely what he | > needed to hear, since he should look for the reasons in his own | > customizations. | | This is the fourth time in this thread that I've been told that I must | have turned on the features myself. This is in direct conflict with | the information I provided in the original post. The strange behavior | started after a version upgrade, _not_ after hacking around in my | .emacs file, fooling with any customization options, or anything. I've seen several cases where a customization in ~/.emacs that's been there for years (and across several major versions) suddenly stops working. That is, the variable might be changed or renamed, and so the customization that used to work so well suddenly doesn't. This is especially common with language or character set settings for people outside the 7-bit world. What I'm trying to say is that the reasons some people might have for saying "It's your customizations" are more diverse than they might appear. | I object to being told that I must be mistaken about the basic facts | of what happened in my office yesterday. I'm prepared to guarantee | that my .emacs didn't change one bit in between the time emacs was | behaving "normally" and the time when it started exhibiting "strange" | behavior. As I explain above, sometimes a change in ~/.emacs isn't necessary to provoke such strangeness. | * Thomas A. Horsley wrote: | | > As far as new features being on by default goes, I can understand | > why leaving them on might be a good idea. If I hate them it gives me | > an incentive to read up on them to figure out how to turn them off, | > and if I like them, I'd probably never see them unless they were on | > by default, | | True, but I think a good compromise would be Joe Corneli's idea in the | post he referenced where new features would be "tentatively" turned on | and would explain what they're doing, perhaps in the minibuffer, when | they do something that could be considered "strange." This could also | include instructions about how to turn the behavior off. This would be similar to the features that are currently "disabled" for new users, such as scroll-left. -- SB