From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "John Russell \(jorussel\)" Newsgroups: gmane.emacs.devel Subject: RE: FW: Emacs non-ascii characters Date: Mon, 21 Nov 2005 18:36:55 -0500 Message-ID: <735F40E0DE95EE4B9AF8DADC87E73EA9195442@xmb-rtp-206.amer.cisco.com> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1701377911==" X-Trace: sea.gmane.org 1132620266 13001 80.91.229.2 (22 Nov 2005 00:44:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 22 Nov 2005 00:44:26 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 22 01:44:23 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EeMFW-0001UX-0p for ged-emacs-devel@m.gmane.org; Tue, 22 Nov 2005 01:43:06 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EeMFU-0002u6-LB for ged-emacs-devel@m.gmane.org; Mon, 21 Nov 2005 19:43:05 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EeLGG-0007ng-8I for emacs-devel@gnu.org; Mon, 21 Nov 2005 18:39:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EeLGD-0007ml-Ub for emacs-devel@gnu.org; Mon, 21 Nov 2005 18:39:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EeLGD-0007mh-Po for emacs-devel@gnu.org; Mon, 21 Nov 2005 18:39:45 -0500 Original-Received: from [64.102.122.149] (helo=rtp-iport-2.cisco.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EeLGD-0008NW-T3 for emacs-devel@gnu.org; Mon, 21 Nov 2005 18:39:46 -0500 Original-Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 21 Nov 2005 18:39:44 -0500 X-IronPort-AV: i="3.97,358,1125892800"; d="scan'208,217"; a="76262619:sNHT35934360" Original-Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jALNdYlt022581; Mon, 21 Nov 2005 18:39:42 -0500 (EST) Original-Received: from xmb-rtp-206.amer.cisco.com ([64.102.31.32]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 21 Nov 2005 18:39:37 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FW: Emacs non-ascii characters Thread-Index: AcXu8z8BTnzgDgyBQuayvHMCAKkmlgAATY88 Original-To: "Drew Adams" , X-OriginalArrivalTime: 21 Nov 2005 23:39:37.0299 (UTC) FILETIME=[D599E230:01C5EEF4] 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:46419 Archived-At: This is a multi-part message in MIME format. --===============1701377911== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5EEF4.D4CF5A15" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5EEF4.D4CF5A15 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have to say, now that I know what happened this will never really bug = me again, but sweet Jahosafat it was annoying for a long time until I = asked the list. I think that that this could be handled like = set-goal-column or downcase-region or upcase-region or narrow-to-region = all of which need to be manually disabled once. They all fit the same = mold. Some really useful and seemingly innocuous feature that could = confuse the smack out of some poor unsuspecting user. =20 =20 John =20 ________________________________ From: Drew Adams [mailto:drew.adams@oracle.com] Sent: Mon 2005-11-21 18:27 To: emacs-devel@gnu.org Cc: John Russell (jorussel) Subject: RE: FW: Emacs non-ascii characters Perhaps if the current locale is en_US (and other en variants, since many use the US layout and have little need for input methods), then C-\ should not automatically select an input method the first time it is hit. Then the user will be prompted and can hit C-g. This will = overcome the problem that if it is hit by accident by someone who knows = nothing about input methods, they have no way of knowing what has gone = wrong. That sounds like a good approach, provided the initial prompt were only asked the first time (and the setting remembered persistently, via Customize). But again, I can't speak for people who use this. Would en_US users who = use `C-\' be bothered by an initial prompt? ------_=_NextPart_001_01C5EEF4.D4CF5A15 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= RE: FW: Emacs non-ascii characters=0A= =0A= =0A=
=0A=
I have to = say, now that I =0A= know what happened this will never really bug me again, but sweet = Jahosafat it =0A= was annoying for a long time until I asked the list.  I think = that =0A= that this could be handled like set-goal-column or downcase-region or =0A= upcase-region or narrow-to-region all of which need to be manually = disabled =0A= once.  They all fit the same mold.  Some really useful and = seemingly =0A= innocuous feature that could confuse the smack out of some poor = unsuspecting =0A= user. 
=0A=
 
=0A=
John
=0A=
 
=0A=

=0A=
=0A= From: Drew Adams =0A= [mailto:drew.adams@oracle.com]
Sent: Mon 2005-11-21 =0A= 18:27
To: emacs-devel@gnu.org
Cc: John Russell =0A= (jorussel)
Subject: RE: FW: Emacs non-ascii =0A= characters

=0A=
=0A=

    Perhaps if the current locale is = en_US (and =0A= other en variants, since
    many use the US layout = and have =0A= little need for input methods),
    then =0A= C-\
    should not automatically select an input = method the =0A= first time it is
    hit. Then the user will be = prompted and =0A= can hit C-g. This will overcome
    the problem that = if it is =0A= hit by accident by someone who knows nothing
    about = input =0A= methods, they have no way of knowing what has gone wrong.

That = sounds =0A= like a good approach, provided the initial prompt were only
asked the = first =0A= time (and the setting remembered persistently, = via
Customize).

But =0A= again, I can't speak for people who use this. Would en_US users who = use
`C-\' =0A= be bothered by an initial prompt?

=0A= =0A= =0A= ------_=_NextPart_001_01C5EEF4.D4CF5A15-- --===============1701377911== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============1701377911==--