From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Rupert Newsgroups: gmane.emacs.help Subject: =?iso-8859-1?q?Re=3A_predictive_mode_and_=27=E3=27?= Date: Sun, 15 Jul 2007 00:42:22 -0000 Organization: http://groups.google.com Message-ID: <1184460142.458475.103180@q75g2000hsh.googlegroups.com> References: <1184333068.581937.161990@r34g2000hsd.googlegroups.com> <87r6nb5m34.wl@nospam.anselm.chemie.fu-berlin.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1184507889 3575 80.91.229.12 (15 Jul 2007 13:58:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 15 Jul 2007 13:58:09 +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 Jul 15 15:58:06 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IA4bu-00047m-5d for geh-help-gnu-emacs@m.gmane.org; Sun, 15 Jul 2007 15:58:06 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IA4bt-00073n-Rs for geh-help-gnu-emacs@m.gmane.org; Sun, 15 Jul 2007 09:58:05 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!q75g2000hsh.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 43 Original-NNTP-Posting-Host: 81.76.11.132 Original-X-Trace: posting.google.com 1184460142 4063 127.0.0.1 (15 Jul 2007 00:42:22 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sun, 15 Jul 2007 00:42:22 +0000 (UTC) In-Reply-To: <87r6nb5m34.wl@nospam.anselm.chemie.fu-berlin.de> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.4) Gecko/20070508 Iceweasel/2.0.0.4 (Debian-2.0.0.4-1),gzip(gfe),gzip(gfe) X-HTTP-Via: rupertlaptop:3128 (Oops 1.5.23) Complaints-To: groups-abuse@google.com Injection-Info: q75g2000hsh.googlegroups.com; posting-host=81.76.11.132; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Original-Xref: shelby.stanford.edu gnu.emacs.help:150103 X-Mailman-Approved-At: Sun, 15 Jul 2007 09:57:49 -0400 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:45691 Archived-At: On Jul 14, 11:14 am, Anselm Helbig wrote: > > I haven't used predictive mode yet, so I can't comment on that. But > the usual way emacs determines if some character belongs to a word or > not is by syntax tables; these tables are mode-specific. When I put > point on the letter `=E3', `C-u C-x =3D' gives me some information about > the character (I'm using GNU Emacs 22), and it says that it's syntax > is "w which means: word". > > What emacs are you using, and what mode are you in? Does M-f > (forward-word) and M-b (backward-word) stop at accented characters? > Maybe you can do something about it by fiddling with the syntax > table (look them up in the elisp manual). > > HTH, > > Anselm Could it be that the predictive mode is interpreting your hitting the ~ key as an input of "~" (which would end the word, as it's punctuation)? Then you'd get the rubbish completion you're describing. Once you type the following a, however, the string "~a" is squished into just "=E3" and so you end up with "n=E3o", which emacs correctly once again decides is a single word. The fundamental problem seems to be that predictive mode has no way of knowing which bit of a "multi-key character" is the last bit and thus at which point it should decide whether to expand. Maybe there's a different hook that predictive mode could be using (does emacs send out one when it finally decides on a character?) A work-around might be to have a look at different input systems you might use: 1) If you're in X, you could set, say, your Alt-Gr key to act as compose. Then you could type something like Alt-Gr ~, a 2) Possibly faster to type with: I know that the German entry mode for emacs has a "post" form, so you can type =E4 by ae. Is there a Portuguese mode similar? Then the punctuation would happen after the letter and maybe predictive mode wouldn't get confused. Rupert