From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.help Subject: Re: Is Emacs becoming Word? Date: Sat, 26 Mar 2005 12:14:04 +0100 Organization: Organization?!? Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1111835966 5153 80.91.229.2 (26 Mar 2005 11:19:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 26 Mar 2005 11:19:26 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Mar 26 12:19:25 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DF9K6-0003Nd-Bm for geh-help-gnu-emacs@m.gmane.org; Sat, 26 Mar 2005 12:19:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DF9Zd-00051t-Ru for geh-help-gnu-emacs@m.gmane.org; Sat, 26 Mar 2005 06:35:26 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 81 Original-X-Trace: individual.net pAZKIZwZ5/m9xMeUCLp3owsISFotnoSYwh2UIBhz/v2L523NgE X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:xyIxrGeeEjs+EZS0oc3gW2TtpjI= Original-Xref: shelby.stanford.edu gnu.emacs.help:129629 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 X-MailScanner-To: geh-help-gnu-emacs@m.gmane.org Xref: news.gmane.org gmane.emacs.help:25180 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:25180 Greg Novak writes: > * David Kastrup wrote: >>> Today when I was editing source code and tried to type pi/2 in a >>> buffer, Emacs replaced it with some special character that appeared >>> as "1/2" as a single character. >> Unlikely. Let me name a few things that might have happened: >> a) you use Leim (C-\) for input of international characters and the >> transliteration for ½ is /2. Leim is not on unless you enable it. It >> should be easy to find an input method that suits your bill better. >> b) you use font-lock-mode in LaTeX and write something like ^2, in >> which case a subscript 2 appears. font-lock-mode is not turned on by >> default. Even if you turn it on, you can remove the script >> highlighting. > > None of the above? I've never (intentionally) used Leim, and I didn't > type C-\ before the /2. Typing it once in the buffer is sufficient. Your mode line will then show a "1" pretty much at the start, and the corresponding tooltip will explain this is the "latin-1" input encoding. > I had font-lock-mode on, but wasn't in Latex mode. I was in Python > mode, and I typed nothing other than pi/2, which got translated to > "pi(one_half_as_one_character)" Again: input encodings don't switch themselves onall by themselves. > And another thing: when I type " or ', Emacs seems to think that I'm > trying to input a special character. If I type 'a, I get an angstrom > symbol, even though (again) I'm editing python code and I'm just > trying to type a string that starts with a. You have the latin-1 input encoding enabled. This does not happen automatically. You can verify this by calling emacs -q and then editing a Python file: that should give you the out-of-the-box configuration of Emacs (plus site-wide configurations). And if you suspect the site-wide configuration, try emacs -q -no-site-file instead. Again: Emacs is not doing anything by default here. _You_ or your packager are doing something here. >>> The other day I was editing Lisp code and found that instead of the >>> usual paren highlighting, Emacs was highlighting the entire enclosed >>> expression. >> I don't get that here. What did you switch on to get it? > > This suddenly appeared after updating software, in this case on an > OS X machine. I didn't enable any switch (myself), I just got it. Again: this is not an Emacs default. You are likely using some customization that the one responsible for packaging Emacs thinks a good idea. Complain to your packager. >> But they are rarely on by default. > > I'm afraid I have to disagree. All three of the above issues > appeared after version upgrades: the first two on a Linux machine, > the last on an OS X laptop. They are off by default, really. The Emacs default is what you get with emacs -q -no-site-file > Maybe there are 3000 new features, and these are the three that are > on by default, in which case I guess you'd be right, in principle. No, really. Please try out emacs -q -no-site-file. _That_'s the state you can complain about to Emacs developers. All the rest is somebody else's responsibility. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum