From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: xah lee Newsgroups: gmane.emacs.help Subject: Re: bug#1406: backward-up-list reports scan error incorrectly? Date: Thu, 27 Nov 2008 07:56:17 -0800 Message-ID: References: <20081121231944.GB2089@muc.de> <5F3AB054-C158-4518-9C93-6938EB2D123D@xahlee.org> <20081122123644.GA3330@muc.de> <12CBE034-485F-49CE-9EF6-2C33A51AF0C1@xahlee.org> <9331FB10-71C6-4B1B-94B6-B5C9B3667B74@xahlee.org> <20081122140446.GC3330@muc.de> <20081127121951.GA3137@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1227815858 15079 80.91.229.12 (27 Nov 2008 19:57:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Nov 2008 19:57:38 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Alan Mackenzie Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Nov 27 20:58:39 2008 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 1L5n0R-0005Ze-It for geh-help-gnu-emacs@m.gmane.org; Thu, 27 Nov 2008 20:58:31 +0100 Original-Received: from localhost ([127.0.0.1]:60602 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L5mzH-0008Gq-Ll for geh-help-gnu-emacs@m.gmane.org; Thu, 27 Nov 2008 14:57:19 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L5jEN-0001oF-HD for help-gnu-emacs@gnu.org; Thu, 27 Nov 2008 10:56:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L5jEK-0001n5-8P for help-gnu-emacs@gnu.org; Thu, 27 Nov 2008 10:56:38 -0500 Original-Received: from [199.232.76.173] (port=42822 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L5jEK-0001mu-28 for help-gnu-emacs@gnu.org; Thu, 27 Nov 2008 10:56:36 -0500 Original-Received: from mout.perfora.net ([74.208.4.194]:61589) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L5jEJ-0003MA-Df for help-gnu-emacs@gnu.org; Thu, 27 Nov 2008 10:56:35 -0500 Original-Received: from [192.168.1.2] (c-24-6-185-159.hsd1.ca.comcast.net [24.6.185.159]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1L5jE314HL-0001Lb; Thu, 27 Nov 2008 10:56:22 -0500 In-Reply-To: <20081127121951.GA3137@muc.de> X-Mailer: Apple Mail (2.753.1) X-Provags-ID: V01U2FsdGVkX19FHXyQE/SGVPHLjIZyNmio8me5huM19drsPdZ 6TwQYGmKC2cdLbs5F94zQqD1nlX6Y6Ew6zOpbyOKOXjnaLr3g8 VyAuzWtsy5fccPdKDJULQ== X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-Mailman-Approved-At: Thu, 27 Nov 2008 14:56:57 -0500 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:60161 Archived-At: On Nov 27, 4:19 am, Alan Mackenzie wrote: > Hi, Xah! > > > > though, isn't this something easy to fix? > > No, because it isn't a bug. It's the way the function is meant =20 to work. > > If there is a bug, it's that the doc-string (and maybe the elisp =20= manual, > > I haven't looked) is vague and incomplete. > > I've amended the Emacs manual (.../doc/emacs/programs.texi) and =20 the doc > strings of `backward-up-list' and several similar functions > (.../lisp/emacs-lisp/lisp.el). > > If you're interested, have a look at the changes in > . Thanks Alan. I'd rather hope for a fix instead of change wording to reflect =20 current situation. You argued in bug list that the issue is not simple essentially due =20 to the fact that straight quote chars are not matching pairs. That is true, but i think given today's tech and computing power, we =20 can over come this. Just assume that double quotes in the source code =20= are matched, since they are most of the time. In the few cases when =20 the backward-up-list went to the wrong place due to un-matched double =20= quote, i think that's ok. (as opposed to, it stops dead and utter a =20 beep.) alternatively, if the cursor is inside double quote, then issue a =20 warning in the messag area that the result may not be correct. Also, since this works in text-mode, so apparently this can work. A =20 implementation is to temporarily switch to that mode, do the cursor =20 move, then switch back. Or temp set the syntax table to whatever chat =20= that made text-mode work and emacs-lisp-mode not work. In general, my feeling is that moving around nested pairs is not a =20 some insurmountable issue, that given today's technology and =20 software, it seems wimpy to tell users that backward-up-list won't =20 work if it's inside double quotes. Much complex problems are solved =20 today in emacs, in other IDEs, etc. Just my opinions. Thanks. Xah =E2=88=91 http://xahlee.org/ =E2=98=84 On Nov 27, 2008, at 4:19 AM, Alan Mackenzie wrote: Hi, Xah! >> though, isn't this something easy to fix? > No, because it isn't a bug. It's the way the function is meant to =20 > work. > If there is a bug, it's that the doc-string (and maybe the elisp =20 > manual, > I haven't looked) is vague and incomplete. I've amended the Emacs manual (.../doc/emacs/programs.texi) and the doc strings of `backward-up-list' and several similar functions (.../lisp/emacs-lisp/lisp.el). If you're interested, have a look at the changes in . --=20 Alan Mackenzie (Nuremberg, Germany). =E2=98=84